Method and apparatus for dynamically configuring channel loss measurement in next-generation mobile communication system

ABSTRACT

A communication method and system for converging a 5 th  generation (5G) communication system for supporting higher data rates beyond a 4 th  generation (4G) system with a technology for Internet of Things (IoT) is provided. The disclosure relates to an intelligent services based on the 5G communication technology and the IoT-related technology, such as smart home, smart building, smart city, smart car, connected car, health care, digital education, smart retail, security and safety services. Further, a method and an apparatus for dynamically configuring channel loss measurement is provided.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application a continuation application of prior application Ser.No. 17/036,634, filed on Sep. 29, 2020, which was based on and claimedpriority under 35 U.S.C. 119(a) of a Korean patent application number10-2019-0141959 filed on Nov. 7, 2019, in the Korean IntellectualProperty Office, and of a Korean patent application number10-2019-0169900, filed on Dec. 18, 2019, in the Korean IntellectualProperty Office, the disclosure of each of which is incorporated byreference herein in its entirety.

BACKGROUND 1. Field

The disclosure relates to the operations of a user equipment (UE) and abase station in a mobile communication system. More particularly, thedisclosure relates to improving a method of measuring and applying pathloss using a multiple-input and multiple-output (MIMO) capability in anext-generation mobile communication system by using a beam.

2. Description of Related Art

To meet the demand for wireless data traffic having increased sincedeployment of 4^(th) generation (4G) communication systems, efforts havebeen made to develop an improved 5^(th) generation (5G) or pre-5Gcommunication system. Therefore, the 5G or pre-5G communication systemis also called a ‘Beyond 4G Network’ or a ‘Post long-term evolution(LTE) System’. The 5G communication system is considered to beimplemented in higher frequency millimeter (mm) Wave bands, e.g., 60gigahertz (GHz) bands, so as to accomplish higher data rates. Todecrease propagation loss of the radio waves and increase thetransmission distance, the beamforming, massive multiple-inputmultiple-output (MIMO), Full Dimensional MIMO (FD-MIMO), array antenna,an analog beam forming, large scale antenna techniques are discussed in5G communication systems. In addition, in 5G communication systems,development for system network improvement is under way based onadvanced small cells, cloud Radio Access Networks (RANs), ultra-densenetworks, device-to-device (D2D) communication, wireless backhaul,moving network, cooperative communication, Coordinated Multi-Points(CoMP), reception-end interference cancellation and the like. In the 5Gcommunication system, Hybrid FSK and QAM Modulation (FQAM) and slidingwindow superposition coding (SWSC) as an advanced coding modulation(ACM), and filter bank multi carrier (FBMC), non-orthogonal multipleaccess (NOMA), and sparse code multiple access (SCMA) as an advancedaccess technology have been developed.

The Internet, which is a human centered connectivity network wherehumans generate and consume information, is now evolving to the Internetof Things (IoT) where distributed entities, such as things, exchange andprocess information without human intervention. The Internet ofEverything (IoE), which is a combination of the IoT technology and theBig Data processing technology through connection with a cloud server,has emerged. As technology elements, such as “sensing technology”,“wired/wireless communication and network infrastructure”, “serviceinterface technology”, and “Security technology” have been demanded forIoT implementation, a sensor network, a Machine-to-Machine (M2M)communication, Machine Type Communication (MTC), and so forth have beenrecently researched. Such an IoT environment may provide intelligentInternet technology services that create a new value to human life bycollecting and analyzing data generated among connected things. IoT maybe applied to a variety of fields including smart home, smart building,smart city, smart car or connected cars, smart grid, health care, smartappliances and advanced medical services through convergence andcombination between existing Information Technology (IT) and variousindustrial applications.

In line with this, various attempts have been made to apply 5Gcommunication systems to IoT networks. For example, technologies such asa sensor network, Machine Type Communication (MTC), andMachine-to-Machine (M2M) communication may be implemented bybeamforming, MIMO, and array antennas. Application of a cloud RadioAccess Network (RAN) as the above-described Big Data processingtechnology may also be considered to be as an example of convergencebetween the 5G technology and the IoT technology.

There is a need for a method for updating beam information in relationto an operation of a terminal configuring and activating beaminformation (spatial relation) used for physical uplink control channel(PUCCH) transmission.

The above information is presented as background information only toassist with an understanding of the disclosure. No determination hasbeen made, and no assertion is made, as to whether any of the abovemight be applicable as prior art with regard to the disclosure.

SUMMARY

Aspects of the disclosure are to address at least the above-mentionedproblems and/or disadvantages and to provide at least the advantagesdescribed below. Accordingly, an aspect of the disclosure is to providea method for improving an existing method of measuring and applying pathloss using a multiple-input and multiple-output (MIMO) capability in anext-generation mobile communication system using a beam, particularlyin a method in which a user equipment (UE) measures path loss in acommunication channel and applies the pass loss. In particular, passloss measurement may be increased due to an increase in the number oftransmission and reception antennas of a UE, and an operation ofdynamically updating valid path loss measurement may be needed.

Additional aspects will be set forth in part in the description whichfollows and, in part, will be apparent from the description, or may belearned by practice of the presented embodiments.

Further, the disclosure relates to an operation of a UE configuring andactivating beam information (spatial relation) used for physical uplinkcontrol channel (PUCCH) transmission in a next-generation mobilecommunication system using a beam. Generally, it is possible to updateor indicate a beam (spatial relation) through a single medium accesscontrol (MAC) control element (MAC CE) for a PUCCH resource in aspecific bandwidth part (BWP) within one serving cell. However, since aplurality of PUCCH resources may be configured in one serving cell and aBWP, a plurality of MAC CE transmissions is required to update beaminformation about all the configured PUCCH resources, thus causing anincrease in signaling and latency time.

Technical tasks to be achieved in the disclosure are not limited to thetechnical aspects mentioned above, and other technical aspects notmentioned will be clearly understood by those skilled in the art fromthe following description.

According to an embodiment, it is possible to dynamically measure andapply a plurality of path loss resources configured by a base station ina next-generation mobile communication system using a beam, particularlyin a method in which a UE measures path loss in a communication channeland applies the pass loss.

Further, beam information applied to transmission of a PUCCH resourceconfigured in a BWP of a serving cell may be updated by being commonlyapplied to a plurality of PUCCH resources rather than being indicatedper individual PUCCH resource in a next-generation mobile communicationsystem, thereby reducing latency time in applying a correspondingconfiguration and reducing signaling overhead for the update.

Other aspects, advantages, and salient features of the disclosure willbecome apparent to those skilled in the art from the following detaileddescription, which, taken in conjunction with the annexed drawings,discloses various embodiments of the disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects, features, and advantages of certainembodiments of the disclosure will be more apparent from the followingdescription taken in conjunction with the accompanying drawings, inwhich:

FIG. 1 illustrates a structure of an LTE system according to anembodiment of the disclosure;

FIG. 2 illustrates a wireless protocol structure of an LTE systemaccording to an embodiment of the disclosure;

FIG. 3 illustrates a structure of a next-generation mobile communicationsystem according to an embodiment of the disclosure;

FIG. 4 illustrates a wireless protocol structure of a next-generationmobile communication system according to an embodiment of thedisclosure;

FIG. 5 illustrates a structure of a next-generation mobile communicationsystem according to an embodiment of the disclosure;

FIG. 6 illustrates a frame structure used by a new radio (NR) systemaccording to an embodiment of the disclosure;

FIG. 7 illustrates a scenario of a measurement resource type and anindication for a path loss reference signal (hereinafter, “path lossreference signal (RS)”) configured in a physical uplink shared channel(PUSCH) in an NR system according to an embodiment of the disclosure;

FIG. 8 illustrates an overall operation of a UE for a measurementresource type and an indication for a path loss RS configured in a PUSCHin an NR system according to an embodiment of the disclosure;

FIG. 9 illustrates a scenario of a measurement resource type, dynamicmapping updating, and a valid resource indication for a plurality ofpath loss RSs configured in a PUSCH in an NR system according to anembodiment of the disclosure;

FIG. 10 illustrates an overall UE operation for a measurement resourcetype, dynamic mapping updating, and a valid resource indication for aplurality of path loss RSs configured in a PUSCH according to anembodiment of the disclosure;

FIG. 11 illustrates a first MAC CE and a first mapping method fordynamic updating of a path loss RS requiring measurement according to anembodiment of the disclosure;

FIG. 12 illustrates a second MAC CE and a second mapping method fordynamic updating of a path loss RS requiring measurement according to anembodiment of the disclosure;

FIG. 13 illustrates an overall UE operation for a measurement resourcetype and dynamic resource indication for a path loss RS configured in asound reference signal (SRS) transmission according to an embodiment ofthe disclosure;

FIG. 14 illustrates an MAC CE and a mapping method for dynamic updatingof a path loss RS requiring measurement according to an embodiment ofthe disclosure;

FIG. 15 illustrates an overall operation of a measurement andapplication of a path loss RS for PUSCH and SRS transmission accordingto an embodiment of the disclosure;

FIG. 16 illustrates an overall operation of a base station according toan embodiment of the disclosure;

FIG. 17 illustrates a structure of a next-generation mobilecommunication system and a scenario in which a PUCCH resourceconfiguration and a beam activation operation are applied according toan embodiment of the disclosure;

FIG. 18 illustrates an overall operation of simultaneously updatingtransmission beams by grouping a plurality of PUCCH resources configuredthrough a plurality of serving cells and a BWP in an NR system accordingto an embodiment of the disclosure;

FIG. 19 illustrates a UE operation of configuring a PUCCH resource groupvia a radio resource control (RRC) control message and applyingsimultaneous beam updating for the PUCCH resource group through an MACCE according to an embodiment of the disclosure;

FIG. 20 illustrates an overall UE operation of supporting simultaneousbeam updating for a PUCCH resource group through an MAC CE according toan embodiment of the disclosure;

FIG. 21 illustrates an MAC CE structure according to an embodiment ofthe disclosure;

FIG. 22 illustrates an MAC CE structure according to an embodiment ofthe disclosure;

FIG. 23 illustrates an MAC CE structure according to an embodiment ofthe disclosure;

FIG. 24 illustrates an MAC CE structure according to an embodiment ofthe disclosure;

FIG. 25 illustrates an MAC CE structure according to an embodiment ofthe disclosure;

FIG. 26 illustrates an MAC CE structure according to an embodiment ofthe disclosure;

FIG. 27 illustrates the overall operation of a base station according toan according to an embodiment of the disclosure;

FIG. 28 is a block diagram illustrating an internal structure of a UEaccording to an embodiment of the disclosure; and

FIG. 29 is a block diagram illustrating a configuration of an NR basestation according to an embodiment of the disclosure.

DETAILED DESCRIPTION

The following description with reference to the accompanying drawings isprovided to assist in a comprehensive understanding of variousembodiments of the disclosure as defined by the claims and theirequivalents. It includes various specific detailed to assist in thatunderstanding but these are to be regarded as merely exemplary.Accordingly, those of ordinary skill in the art will recognize thatvarious changes and modifications of the various embodiments describedherein can be made without departing from the scope and spirit of thedisclosure. In addition, descriptions of well-known functions andconstructions may be omitted for clarity and conciseness.

The terms and words used in the following description and claims are notlimited to the bibliographical meanings, but, are merely used by theinventor to enable a clear and consistent understanding of thedisclosure. Accordingly, it should be apparent to those skilled in theart that the following description of various embodiments of thedisclosure is provided for illustration purpose only and not for thepurpose of limiting the disclosure as defined by the appended claims andtheir equivalents.

It is to be understood that the singular forms “a,” “an,” and “the”include plural referents unless the context clearly dictates otherwise.Thus, for example, reference to “a component surface” includes referenceto one or more of such surfaces.

Hereinafter, for convenience of explanation, terms and designationsdefined in 3rd Generation Partnership Project Long-Term Evolution (3GPPLTE) standards are used in the disclosure. However, the disclosure isnot limited by those terms and designations but may be equally appliedto systems in accordance with other standards.

FIG. 1 illustrates a structure of an LTE system according to anembodiment of the disclosure.

Referring to FIG. 1 , a radio access network of the LTE system mayinclude an evolved node B (hereinafter, “eNB”, “Node B”, or “basestation”) 105, 110, 115, or 120, a mobility management entity (MME) 125,and a serving gateway (S-GW) 130. A user equipment (hereinafter, “UE” or“terminal”) 135 accesses an external network through the eNBs 105, 110,115, and 120 and the S-GW 130.

Referring to FIG. 1 , the eNBs 105, 110, 115, and 120 correspond toexisting nodes B of a universal mobile telecommunications system (UMTS).The eNBs 105, 110, 115, and 120 are connected to the UE 135 over awireless channel and perform a more complex role than that of theexisting Nodes B. In the LTE system, all user traffic including areal-time service, such as a voice over Internet protocol (VoIP)service, is provided through a shared channel. Therefore, a device thatcollects state information, such as buffer status, availabletransmission power state, and channel state of UEs (e.g., the UE 135),and performs scheduling is required. The eNBs 105, 110, 115, and 120 areresponsible for these functions. One eNB 105, 110, 115, or 120 generallycontrols a plurality of cells. For example, in order to realize atransmission speed of 100 Mbps, the LTE system uses orthogonal frequencydivision multiplexing (hereinafter, “OFDM”) as a radio accesstechnology, for example, at a bandwidth of 20 megahertz (MHz). Inaddition, the LTE system applies adaptive modulation & coding(hereinafter, “AMC”), which determines a modulation scheme and a channelcoding rate according to the channel state of the UE 135. The S-GW 130is a device that provides a data bearer and generates or removes a databearer under the control of the MME 125. The MME 125 is a device thatperforms not only a mobility management function for the UE 135 but alsovarious control functions and is connected to a plurality of basestations 105, 110, 115, and 120.

FIG. 2 illustrates a wireless protocol structure of an LTE systemaccording to an embodiment of the disclosure.

Referring to FIG. 2 , a wireless protocol of the LTE system includespacket data convergence protocols (PDCPs) 205 and 240, radio linkcontrols (RLCs) 210 and 235, and medium access controls (MACs) 215 and230 respectively in a UE and an eNB. The PDCPs 205 and 240 areresponsible for IP header compression/decompression or the like. Mainfunctions of the PDCPs 205 and 240 are summarized as follows.

-   -   Header compression and decompression (robust header compression        (ROHC) only)    -   Transfer of user data    -   In-sequence delivery of upper-layer PDUs at PDCP        re-establishment procedure for RLC AM    -   For split bearers in DC (only support for RLC AM), PDCP PDU        routing for transmission and PDCP PDU reordering for reception    -   Duplicate detection of lower-layer SDUs at PDCP re-establishment        procedure for RLC AM    -   Retransmission of PDCP SDUs at handover and, for split bearers        in DC, of PDCP PDUs at PDCP data-recovery procedure, for RLC AM    -   Ciphering and deciphering    -   Timer-based SDU discard in uplink

The radio link controls (hereinafter, “RLCs”) 210 and 235 reconstructs aPDCP packet data unit (PDU) into a proper size and performs an automaticrepeat request (ARQ) operation. Main functions of the RLCs 210 and 235are summarized as follows.

-   -   Transfer of upper-layer PDUs    -   Error Correction through ARQ (only for AM data transfer)    -   Concatenation, segmentation, and reassembly of RLC SDUs (only        for UM and AM data transfer)    -   Re-segmentation of RLC data PDUs (only for AM data transfer)    -   Reordering of RLC data PDUs (only for UM and AM data transfer)    -   Duplicate detection (only for UM and AM data transfer)    -   Protocol error detection (only for AM data transfer)    -   RLC SDU discard (only for UM and AM data transfer)    -   RLC re-establishment

The MACs 215 and 230 are connected to a plurality of RLC-layer devicesconfigured in one UE, multiplex RLC PDUs into a MAC PDU, and demultiplexan MAC PDU into RLC PDUs. Main functions of the MACs 215 and 230 aresummarized as follows.

-   -   Mapping between logical channels and transport channels    -   Multiplexing/demultiplexing of MAC SDUs belonging to one or        different logical channels into/from Transport Blocks (TBs)        delivered to/from the physical layer on transport channels    -   Scheduling information reporting    -   Error correction through HARQ    -   Priority handling between logical channels of one UE    -   Priority handling between UEs by means of dynamic scheduling    -   Multimedia broadcast/Multicast (MBMS) service identification    -   Transport format selection    -   Padding

Physical (PHY) layers 220 and 225 perform channel coding and modulationof upper-layer data and convert the data into OFDM symbols to transmitthe OFDM symbols via a wireless channel, or demodulate OFDM symbolsreceived via a wireless channel and perform channel decoding of the OFDMsymbols to deliver the OFDM symbols to an upper layer. The PHY layers220 and 225 also use hybrid ARQ (HARQ) for additional error correction,in which a receiver transmits one bit to indicate whether a packettransmitted from a transmitter is received. This is referred to as HARQACK/NACK information. Downlink HARQ ACK/NACK information in response touplink transmission may be transmitted through a physical channel, suchas a physical hybrid-ARQ indicator channel (PHICH), and uplink HARQACK/NACK information in response to downlink transmission may betransmitted through a physical channel, such as a physical uplinkcontrol channel (PUCCH) or physical uplink shared channel (PUSCH).

The PHY layers 220 and 225 may include one frequency/carrier or aplurality of frequencies/carriers, and a technology of simultaneouslyconfiguring and using a plurality of frequencies is referred to ascarrier aggregation (hereinafter, “CA”). In CA, instead of using onecarrier, a main carrier and one additional subcarrier or a plurality ofadditional subcarriers is used for communication between a terminal (orUE) and a base station (E-UTRAN NodeB: eNB), thereby dramaticallyincreasing the transmission amount in relation to the number ofsubcarriers. In LTE, a cell of a base station using a main carrier isreferred to as a primary cell (PCell), and a cell using a subcarrier isreferred to as a secondary cell (SCell).

Although not shown in the drawing, a radio resource control(hereinafter, “RRC”) layer exists above the PDCP layer of each of the UEand the base station. The RRC layer may exchange connection andmeasurement-related setup control messages for radio resource control.

FIG. 3 illustrates the structure of a next-generation mobilecommunication system according to an embodiment of the disclosure.

Referring to FIG. 3 , a radio access network of the next-generationmobile communication system includes a new radio node B (hereinafter,“NR NB” or “gNB”) 310 and a new radio core network (NR CN ornext-generation core network (NG CN)) 305. A new radio user equipment(hereinafter, “NR UE” or “terminal”) 315 accesses an external networkthrough the NR gNB 310 and the NR CN 305.

Referring to FIG. 3 , the NR gNB 310 corresponds to an evolved node B(eNB) of an existing LTE system. The NR gNB 310 is connected to the NRUE 315 over a wireless channel and may provide a more advanced servicethan that of the existing node B. In the next-generation mobilecommunication system, all user traffic may be served through a sharedchannel. Therefore, a device that collects state information, such asbuffer status, available transmission power state, and channel state ofUEs (e.g., NR UE 315), and performs scheduling is required. The NR gNB310 is responsible for these functions. One NR gNB 310 generallycontrols a plurality of cells. The next-generation mobile communicationsystem may have a bandwidth greater than the existing maximum bandwidthin order to realize ultrahigh-speed data transmission compared to acurrent LTE. Further, the next-generation mobile communication systemmay employ a beamforming technique in addition to OFDM as a radio accesstechnology. In addition, the next-generation mobile communication systemapplies AMC, which determines a modulation scheme and a channel codingrate according to the channel state of the NR UE 315. The NR CN 305performs functions of mobility support, bearer setup, and quality ofservice (QoS) setup. The NR CN 305 is a device that performs not only amobility management function for the NR UE 315 but also various controlfunctions and is connected to a plurality of base stations (e.g., NR gNB310). The next-generation mobile communication system may also interworkwith the existing LTE system, in which case the NR CN 305 is connectedto an MME 325 through a network interface. The MME 325 is connected toan eNB 330, which is an existing base station.

FIG. 4 illustrates the wireless protocol structure of a next-generationmobile communication system according to an embodiment of thedisclosure.

Referring to FIG. 4 , a wireless protocol of the next-generation mobilecommunication system includes NR SDAPs 401 and 445, NR PDCPs 405 and440, NR RLCs 410 and 435, and NR MACs 415 and 430 respectively at a UEand an NR base station.

Main functions of the NR SDAPs 401 and 445 may include some of thefollowing functions.

-   -   Transfer of user plane data    -   Mapping between QoS flow and DRB for both DL and UL    -   Marking QoS flow ID in both DL and UL packets    -   Reflective QoS flow-to-DRB mapping for UL SDAP PDUs

Regarding the SDAP-layer devices, the UE may receive a configurationabout whether to use a header of the SDAP-layer devices or whether touse a function of the SDAP-layer devices for each PDCP-layer device,each bearer, or each logical channel via an RRC message. When an SDAPheader is configured, a one-bit NAS QoS reflective indicator (NASreflective QoS) and a one-bit AS QoS reflective indicator (AS reflectiveQoS) of the SDAP header may be used for indication to enable the UE toupdate or reconfigure uplink and downlink QoS flows and mappinginformation for a data bearer. The SDAP header may include QoS flow IDinformation indicating QoS. The QoS information may be used as a dataprocessing priority, scheduling information, and the like in order tosupport a desired service.

Main functions of the NR PDCPs 405 and 440 may include some of thefollowing functions.

-   -   Header compression and decompression (ROHC only)    -   Transfer of user data    -   In-sequence delivery of upper-layer PDUs    -   Out-of-sequence delivery of upper-layer PDUs    -   PDCP PDU reordering for reception    -   Duplicate detection of lower-layer SDUs    -   Retransmission of PDCP SDUs    -   Ciphering and deciphering    -   Timer-based SDU discard in uplink.

Among the above functions, the reordering function of the NR PDCPdevices refers to a function of rearranging PDCP PDUs received in alower layer in order on the basis of the PDCP sequence number (SN). Thereordering function of the NR PDCP devices may include a function oftransmitting the data to an upper layer in the order of rearrangement ora function of immediately transmitting the data regardless of the order.In addition, the reordering function may include a function of recordinglost PDCP PDUs via reordering, may include a function of reporting thestate of lost PDCP PDUs to a transmitter, and may include a function ofrequesting retransmission of lost PDCP PDUs.

Main functions of the NR RLCs 410 and 435 may include some of thefollowing functions.

-   -   Transfer of upper-layer PDUs    -   In-sequence delivery of upper-layer PDUs    -   Out-of-sequence delivery of upper-layer PDUs    -   Error Correction through ARQ    -   Concatenation, segmentation, and reassembly of RLC SDUs    -   Re-segmentation of RLC data PDUs    -   Reordering of RLC data PDUs    -   Duplicate detection    -   Protocol error detection    -   RLC SDU discard    -   RLC re-establishment

Among the above functions, the in-sequence delivery function of the NRRLC devices refers to a function of delivering RLC SDUs received from alower layer to an upper layer in order. The in-sequence deliveryfunction of the NR RLC devices may include a function of reassemblingand delivering a plurality of RLC SDUs when one original RLC SDU isdivided into the plurality of RLC SDUs to be received. The in-sequencedelivery function of the NR RLC devices may include a function ofrearranging received RLC PDUs on the basis of the RLC SN or the PDCP SN,may include a function of recording lost RLC PDUs via reordering, mayinclude a function of reporting the state of lost RLC PDUs to atransmitter, and may include a function of requesting retransmission oflost RLC PDUs. If there is a lost RLC SDU, the in-sequence deliveryfunction of the NR RLC devices may include a function of delivering onlyRLC SDUs before the lost RLC SDU to an upper layer in order. Further,the in-sequence delivery function of the NR RLC devices may include afunction of delivering all RLC SDUs, received before a timer starts, toan upper layer in order when the timer has expired despite the presenceof a lost RLC SDU. In addition, the in-sequence delivery function of theNR RLC devices may include a function of delivering all RLC SDUsreceived so far to an upper layer in order when the timer expiresdespite the presence of a lost RLC SDU. The NR RLC devices may processRLC PDUs in order of reception (regardless of the order of sequencenumbers, in order of arrival) and may deliver the RLC PDUs to the PDCPdevices in an out-of-sequence manner. When receiving a segment, the NRRLC devices may receive segments that are stored in a buffer or are tobe received later, may reconstruct the segments into one whole RLC PDU,and may deliver the RLC PDU to the PDCP devices. The NR RLC layers maynot include a concatenation function, and the concatenation function maybe performed in the NR MAC layers or may be replaced with a multiplexingfunction of the NR MAC layers.

The out-of-sequence delivery function of the NR RLC devices refers to afunction of delivering RLC SDUs received from a lower layer directly toan upper layer regardless of order. The out-of-sequence deliveryfunction of the NR RLC devices may include a function of reassemblingand delivering a plurality of RLC SDUs when one original RLC SDU isdivided into the plurality of RLC SDUs to be received. In addition, theout-of-sequence delivery function of the NR RLC devices may include afunction of recording lost RLC PDUs by storing and reordering the RLCSNs or PDCP SNs of received RLC PDUs.

The NR MACs 415 and 430 may be connected to a plurality of NR RLC-layerdevices configured in one device, and main functions of the NR MACs mayinclude some of the following functions.

-   -   Mapping between logical channels and transport channels    -   Multiplexing/demultiplexing of MAC SDUs    -   Scheduling information reporting    -   Error correction through HARQ    -   Priority handling between logical channels of one UE    -   Priority handling between UEs by means of dynamic scheduling    -   MBMS service identification    -   Transport format selection    -   Padding

The NR PHY layers 420 and 425 may perform channel coding and modulationof upper-layer data and convert the data into OFDM symbols to transmitthe OFDM symbols via a wireless channel, or demodulate OFDM symbolsreceived via a wireless channel and perform channel decoding of the OFDMsymbols to deliver the OFDM symbols to an upper layer.

FIG. 5 illustrates the structure of another next-generation mobilecommunication system according to an embodiment of the disclosure.

Referring to FIG. 5 , a cell served by an NR gNB 505 operating based ona beam may include a plurality of transmission and reception points(TRPs) 510, 515, 520, 525, 530, 535, and 540. The TRPs 510, 515, 520,525, 530, 535, and 540 refer to blocks having some functions oftransmitting and receiving physical signals separated from an existingNR base station (eNB) and may include a plurality of antennas. The NRgNB 505 may be represented by a central unit (CU), and the TRPs 510,515, 520, 525, 530, 535, and 540 may be represented by distributed units(DUs). Functions of the NR gNB 505 and the TRPs 510, 515, 520, 525, 530,535, and 540 may be configured by separating individual PDCP/RLC/MAC/PHYlayers (545). That is, the TRPs 515 and 525 may have only a PHY layerand may perform the functions of the PHY layer, and the TRPs 510, 535,and 540 may have only a PHY layer and a MAC layer and may perform thefunctions of the PHY and MAC layers. The TRPs 520 and 530 may have onlya PHY layer, a MAC layer, and an RLC layer and may perform the functionsof the PHY, MAC, and RLC layers. In particular, the TRPs 510, 515, 520,525, 530, 535, and 540 may use a beamforming technique for transmittingand receiving data by generating narrow beams in different directionsusing a plurality of transmission and reception antennas. A UE 550accesses the NR gNB 505 and an external network through the TRPs 510,515, 520, 525, 530, 535, and 540. The NR gNB 505 supports a connectionbetween the UE 550 and a core network (CN), particularly an AMF/SMF 555by collecting state information, such as buffer status, availabletransmission power state, and channel state of the UE 550, andperforming scheduling in order to provide services for users.

FIG. 6 illustrates a frame structure used by an NR system according toan embodiment of the disclosure.

The NR system aims at a higher transmission speed than that in LTE andconsiders a scenario of operating at a high frequency to secure a widefrequency bandwidth. In particular, the NR system considers a scenarioof generating a directional beam at a high frequency and transmittingdata having a high data rate to a UE.

Referring to FIG. 6 , a scenario in which an NR base station or a TRP(e.g., a base station 601) uses different beams when communicating withUEs 671, 673, 675, 677, and 679 in a cell may be considered. That is, inthis illustrated drawing, a scenario is assumed in which UE 1 671 usesbeam #1 651 for communication, UE 2 673 uses beam #5 655 forcommunication, and UE 3 675, UE 4 677, and UE 5 679 use beam #7 657 forcommunication.

In order to measure which beam the UEs 671, 673, 675, 677, and 679 useto communicate with the TRP, an overhead subframe (hereinafter, “osf”603) in which a common overhead signal is transmitted exists in time.The osf 603 may include a primary synchronization signal (PSS) forobtaining timing of an orthogonal frequency division multiplexing (OFDM)symbol, a secondary synchronization signal (SSS) for detecting a cellID, and the like. In addition, the osf 603 may transmit a physicalbroadcast channel (PBCH) including system information, a masterinformation block (MIB), or information essential for a UE to access thesystem (e.g., a bandwidth of a downlink beam, a system frame number, andthe like). Further, in the osf 603, the base station 601 transmits areference signal using a different beam for each symbol (or over aplurality of symbols). The UEs 671, 673, 675, 677, and 679 may derive abeam index value for identifying each beam from the reference signal. Inthis illustrated drawing, it is assumed that there are 12 beams frombeam #1 651 to beam #12 662 transmitted by the base station 601 and adifferent beam is transmitted by sweeping per symbol in the osf 603.That is, an individual beam may be transmitted per symbol in the osf 603(e.g., beam #1 651 is transmitted in a first symbol 631, beam #2 652 istransmitted in a second symbol 632, and the like), and the UEs 671, 673,675, 677, and 679 may measure the osf 603 to measure a beam via whichthe strongest signal is transmitted among beams transmitted in the osf603.

FIG. 6 illustrates a scenario in which the osf 603 is repeated every 25subframes, and remaining 24 subframes are data subframes (hereinafter,“dsf” 605) in which normal data is transmitted and received.Accordingly, it is assumed that, according to scheduling by the basestation 601, UE 3 675, UE 4 677, and UE 5 679 commonly use beam #7 657to perform communication (611), UE 1 671 uses beam #1 651 to performcommunication (613), and UE 2 673 uses beam #5 655 to performcommunication (615). In this illustrated drawing, transmission beam #1651 to transmission beam #12 662 of the base station 601 are mainlyschematized, but reception beams of the UEs 671, 673, 675, 677, and 679(e.g., a first reception beam 681, a second reception beam 683, a thirdreception beam 685, and a fourth reception beam 687 of UE 1 671) forreceiving the transmission beams of the base station 601 may be furtherconsidered. In this illustrated drawing, UE 1 671 has four beams 681,683, 685, and 687 and performs beam sweeping in order to determine whichbeam has the best reception performance. Here, when a plurality of beamscannot be used at the same time, as many osfs 603 as the number ofreception beams may be received using one reception beam for each osf603, thereby finding an optimal transmission beam of the base station601 and an optimal reception beam of the UE 671.

The disclosure describes a method for reducing measurement complexity ofa UE due to an increase in the number of path loss resources that can bemeasured through enhancement of an MIMO function and dynamicallycontrolling measurement of various path loss resources in an existingoperation of measuring a path loss resource in a next-generation mobilecommunication system and determining uplink transmission power in viewof the path loss resource.

Generally, uplink transmission power consumption may be defined asfollows.

Transmission power=Target received power+Path loss+(dynamic adjustment)

As shown above, a UE may determine uplink transmission strength as thesum of the transmission power of a downlink signal received from a basestation, signal strength measured through a path loss reference signal(RS), and a dynamic adjustment having an impact in a UE RF. That is,measurement of the path loss reference signal is necessary to calculatesignal strength for uplink transmission, and a configuration of ameasurement resource type and a method for the measurement is includedin an uplink configuration (e.g., PUSCH-Config, sounding referencesignal (SRS)-Config, or the like). A specific operation will bedescribed in detail in the following embodiments. For reference, themeasurement of the path loss reference signal is an L3 measurement value(determined by the UE in view of both a previous measurement value and acurrent measurement value), in which a measurement window exists.

FIG. 7 illustrates a scenario of a measurement resource type and anindication for a path loss reference signal (hereinafter, “path lossRS”) configured in a PUSCH in an NR system according to an embodiment ofthe disclosure. Particularly, this drawing illustrates an operation inan existing NR system, which may be referred to in an embodimentproposed by the disclosure.

For measurement of a path loss RS applicable to PUSCH transmission, upto four available path loss RS resources may be configured in aPUSCH-Config through a current RRC message, and a UE may measure aconfigured path loss RS and may apply the path loss RS to PUSCHtransmission. That is, the UE determines PUSCH transmission powerconsidering a path loss RS measurement value. An operation ofconfiguring and applying a path loss RS used for PUSCH transmission isas follows.

-   -   1. A path loss RS and mapping information used to indicate a        path loss RS applied to actual PUSCH transmission may be        provided to the UE through an RRC configuration.        -   PUSCH-PathlossReferenceRS: Up to four path loss RSs are            configured        -   Index of a path loss RS        -   Configured as either a CSI-RS resource or an SSB resource        -   The UE performs measurement on configured path loss RSs.        -   SRI-PUSCH-PowerControl: Mapping with a path loss RS used for            actual PUSCH transmission that can be indicated through an            SRS resource indicator (SRI) bit of downlink control            information (DCI) is configured (up to 16 mappings)        -   Index information used to indicate an SRI of PUSCH            transmission        -   Index of a path loss RS associated with an SRI index        -   Specific power configuration (sri-P0-PUSCH-AlphaSetId and            sri-PUSCH-ClosedLoopIndex)

The path loss RS may be configured as below in Table 1.

TABLE 1 PUSCH-PowerControl ::= SEQUENCE {  tpc-Accumulation ENUMERATED {disabled } OPTIONAL, -- Need S  msg3-Alpha Alpha OPTIONAL, -- Need S p0-NominalWithoutGrant INTEGER (−202..24) OPTIONAL, -- Need M p0-AlphaSets SEQUENCE (SIZE (1..maxNrofP0-PUSCH-AlphaSets)) OFP0-PUSCH-AlphaSet OPTIONAL, -- Need M  pathlossReferenceRSToAddModListSEQUENCE (SIZE (1..maxNrofPUSCH- PathlossReferenceRSs)) OFPUSCH-PathlossReferenceRS OPTIONAL, -- Need N pathlossReferenceRSToReleaseList SEQUENCE (SIZE (1..maxNrofPUSCH-PathlossReferenceRSs)) OF PUSCH-PathlossReferenceRS-Id    OPTIONAL, --Need N  twoPUSCH-PC-AdjustmentStates ENUMERATED {twoStates} OPTIONAL, --Need S  deltaMCS ENUMERATED {enabled} OPTIONAL, -- Need S sri-PUSCH-MappingToAddModList SEQUENCE (SIZE (1..maxNrofSRI-PUSCH-Mappings)) OF SRI-PUSCH-PowerControl OPTIONAL, -- Need N sri-PUSCH-MappingToReleaseList SEQUENCE (SIZE (1..maxNrofSRI-PUSCH-Mappings)) OF SRI-PUSCH-PowerControlId    OPTIONAL -- Need N }P0-PUSCH-AlphaSet ::= SEQUENCE {  p0-PUSCH-AlphaSetIdP0-PUSCH-AlphaSetId,  p0 INTEGER (−16..15) OPTIONAL, -- Need S  alphaAlpha OPTIONAL -- Need S } P0-PUSCH-AlphaSetId ::= INTEGER(0..maxNrofP0-PUSCH-AlphaSets-1) PUSCH-PathlossReferenceRS ::= SEQUENCE{  pusch-PathlossReferenceRS-Id PUSCH-PathlossReferenceRS-Id, referenceSignal CHOICE {   ssb-Index SSB-Index,   csi-RS-IndexNZP-CSI-RS-ResourceId  } } PUSCH-PathlossReferenceRS-Id ::= INTEGER(0..maxNrofPUSCH- PathlossReferenceRSs-1) SRI-PUSCH-PowerControl ::=SEQUENCE {  sri-PUSCH-PowerControlId SRI-PUSCH-PowerControlId, sri-PUSCH-PathlossReferenceRS-Id PUSCH-PathlossReferenceRS-Id, sri-P0-PUSCH-AlphaSetId P0-PUSCH-AlphaSetId,  sri-PUSCH-ClosedLoopIndexENUMERATED { i0, i1 } } SRI-PUSCH-PowerControlId ::= INTEGER(0..maxNrofSRI-PUSCH-Mappings-1)

-   -   2. A specific path loss RS used for PUSCH transmission (based on        a codebook or a non-codebook) may be indicated to the UE via an        SRI in DCI format 0_1, which is for specifying one path loss RS        that is actually applied although the UE measures up to four        path loss RSs in phase 1.

Referring to FIG. 7 , as in phase 1, configurations of up to four pathloss RSs that can be configured particularly throughPUSCH-PathlossReferenceRS in PUSCH-Config of the RRC message may beindicated (705, 710, 715, and 720). In addition, path loss RSsassociated with 16 SRIs that can be configured particularly throughSRI-PUSCH-PowerControl in PUSCH-Config of the RRC message may beindicated (725, 727, 729, 731, 733, 735, 737, 739, 741, 743, 745, 747,749, 751, 753, and 755). Mapping between the SRIs and the path loss RSsconfigured through the RRC message is configured, and one path loss RSused for actual PUSCH transmission is indicated via an SRI through DCI.There is no restriction on mapping between the SRIs and the path lossRSs except that up to four path loss RSs can be configured.

FIG. 8 illustrates an overall operation of a UE for a measurementresource type and an indication for a path loss RS configured in a PUSCHin an NR system according to an embodiment of the disclosure.

Referring to FIG. 8 , an operation in an existing NR system, which maybe referred to in an embodiment proposed by the disclosure.

In an RRC-connected state, a UE receives PUSCH configurationinformation, in operation 805, and the configuration information mayprovide path loss RS configuration information required to determinesignal strength and power for PUSCH transmission and configurationinformation about an association between an SRI and a path loss RS.Specific configuration information and a specific operation have beendescribed in detail with reference to FIG. 7 . In operation 810, the UEperforms L3 measurement on up to four path loss RS resources configuredin operation 805 and stores and manages measurement values. In operation815, when a base station indicates scheduling for uplink transmission(PUSCH) of the UE, the base station may indicate not only schedulingresource information but also a specific path loss RS applied tocalculation of signal strength and power for the transmission throughDCI, and the UE may receive the DCI. That is, the base station mayindicate the path loss RS mapped with an SRI of the DCI, and the UE maymeasure a corresponding path loss RS resource and may calculate pathloss. In operation 820, the UE may determine power for a PUSCHtransmission signal considering the pass loss.

FIG. 9 illustrates a scenario of a measurement resource type, dynamicmapping updating, and a valid resource indication for a plurality ofpath loss RSs configured in a PUSCH in an NR system according to anembodiment of the disclosure.

For measurement of a path loss RS applied to PUSCH transmission, a basestation may configure up to 64 path loss RS resources for a UE inPUSCH-Config through an RRC message, and the UE may measure up to fourpath loss RS resources among configured path loss RSs and may apply themeasurement to PUSCH transmission. That is, the UE calculates PUSCHtransmission power in view of a path loss RS measurement value. To thisend, there is a need for a method for indicating a resource initiallymeasured by the UE (up to four resources) even though the base stationconfigures up to 64 path loss RS resources for the UE through an RRCconfiguration. This method is described below. An operation ofconfiguring and applying a path loss RS used for PUSCH transmission isas follows.

-   -   1. A path loss RS and mapping information used to indicate a        path loss RS applied to actual PUSCH transmission may be        provided to the UE through an RRC configuration.        -   PUSCH-PathlossReferenceRS: Up to 64 path loss RSs are            configured        -   Index of a path loss RS        -   Configured as either a CSI-RS resource or an SSB resource        -   SRI-PUSCH-PowerControl: Mapping with a path loss RS used for            actual PUSCH transmission that can be indicated through an            SRI bit of downlink control information (DCI) is configured            (up to 16 mappings)        -   Index information used to indicate an SRI of PUSCH            transmission        -   Index of a path loss RS associated with an SRI index        -   Specific power configuration (sri-P0-PUSCH-AlphaSetId and            sri-PUSCH-ClosedLoopIndex)        -   The above pieces of information are included in a dynamic            mapping update through the following MAC CE        -   Since the UE can measure up to four path loss RSs, the            number of sri-PUSCH-PathlossReferenceRS-Ids associated with            all sri-PUSCH-PowerControlIds is limited to up to four        -   Method for configuring an initially measured path loss RS            through an RRC configuration        -   Method 1: An existing list is used for up to four path loss            RSs to be initially measured, and actual measurement may be            performed for a list for configuring up to 60 path loss RSs            to be newly added only when the list is updated through the            MAC CE        -   Method 2: Up to 64 path loss RSs are configured, and up to            four path loss RSs to be actually measured are limited to            path loss RS resources associated with SRIs configured in            SRI-PUSCH-PowerControl, that is,            sri-PUSCH-PathlossReferenceRS-Id. This limitation is applied            even when information about mapping between the SRIs and the            path loss RSs is updated through the MAC CE

Table 2 and Table 3 are examples for reference in the above description.

TABLE 2 PUSCH-Config ::= SEQUENCE {  dataScramblingIdentityPUSCH INTEGER(0..1023) OPTIONAL, -- Need S  txConfig ENUMERATED {codebook,nonCodebook} OPTIONAL, -- Need S  dmrs-UplinkForPUSCH-MappingTypeASetupRelease { DMRS-UplinkConfig } OPTIONAL, -- Need M dmrs-UplinkForPUSCH-MappingTypeB SetupRelease { DMRS-UplinkConfig }OPTIONAL, -- Need M  pusch-PowerControl PUSCH-PowerControl OPTIONAL, --Need M  frequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, --Need S  frequencyHoppingOffsetLists SEQUENCE (SIZE (1..4)) OF INTEGER(1.. maxNrofPhysicalResourceBlocks-1)     OPTIONAL, -- Need M resourceAllocation ENUMERATED { resourceAllocationType0,resourceAllocationType1, dynamicSwitch},  pusch-TimeDomainAllocationListSetupRelease { PUSCH- TimeDomainResourceAllocationList } OPTIONAL, --Need M  pusch-AggregationFactor ENUMERATED { n2, n4, n8 } OPTIONAL, --Need S  mcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S mcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, --Need S  transformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, --Need S  codebookSubset ENUMERATED {fullyAndPartialAndNonCoherent,partialAndNonCoherent,nonCoherent}    OPTIONAL, -- Cond codebookBased maxRank INTEGER (1..4) OPTIONAL, - - Cond codebookBased  rbg-SizeENUMERATED { config2} OPTIONAL, -- Need S  uci-OnPUSCH SetupRelease {UCI-OnPUSCH} OPTIONAL, -- Need M  tp-pi2BPSK ENUMERATED {enabled}OPTIONAL, -- Need S  ...,   [[ pusch-PowerControl-v16xxPUSCH-PowerControl-v16xx OPTIONAL, -- Need M   ]] }

TABLE 3 PUSCH-PowerControl ::= SEQUENCE {  tpc-Accumulation ENUMERATED {disabled } OPTIONAL, -- Need S  msg3-Alpha Alpha OPTIONAL, -- Need S p0-NominalWithoutGrant INTEGER (−202..24) OPTIONAL, -- Need M p0-AlphaSets SEQUENCE (SIZE (1..maxNrofP0-PUSCH-AlphaSets)) OFP0-PUSCH-AlphaSet OPTIONAL, -- Need M  pathlossReferenceRSToAddModListSEQUENCE (SIZE (1..maxNrofPUSCH- PathlossReferenceRSs)) OFPUSCH-PathlossReferenceRS    OPTIONAL, -- Need N pathlossReferenceRSToReleaseList SEQUENCE (SIZE (1..maxNrofPUSCH-PathlossReferenceRSs)) OF PUSCH-PathlossReferenceRS-Id    OPTIONAL, --Need N  twoPUSCH-PC-AdjustmentStates ENUMERATED {twoStates} OPTIONAL, --Need S  deltaMCS ENUMERATED {enabled} OPTIONAL, -- Need S sri-PUSCH-MappingToAddModList SEQUENCE (SIZE (1..maxNrofSRI-PUSCH-Mappings)) OF SRI-PUSCH-PowerControl    OPTIONAL, -- Need N sri-PUSCH-MappingToReleaseList SEQUENCE (SIZE (1..maxNrofSRI-PUSCH-Mappings)) OF SRI-PUSCH-PowerControlId    OPTIONAL -- Need N } PUSCH-PowerControl-v16xx ::= SEQUENCE {  pathlossReferenceRSToAddModListExt SEQUENCE (SIZE (1..maxNrofPUSCH-PathlossReferenceRSsExt)) OF PUSCH-PathlossReferenceRS    OPTIONAL, --Need N  pathlossReferenceRSToReleaseListExt SEQUENCE (SIZE(1..maxNrofPUSCH- PathlossReferenceRSsExt)) OFPUSCH-PathlossReferenceRS-IdExt    OPTIONAL, -- Need N }P0-PUSCH-AlphaSet ::= SEQUENCE {  p0-PUSCH-AlphaSetIdP0-PUSCH-AlphaSetId,  p0 INTEGER (−16..15) OPTIONAL, -- Need S  alphaAlpha OPTIONAL -- Need S }  SRI-PUSCH-PowerControl ::= SEQUENCE { sri-PUSCH-PowerControlId SRI-PUSCH-PowerControlId, sri-PUSCH-PathlossReferenceRS-Id PUSCH-PathlossReferenceRS-Id, sri-P0-PUSCH-AlphaSetId P0-PUSCH-AlphaSetId,  sri-PUSCH-ClosedLoopIndexENUMERATED { i0, i1 } } P0-PUSCH-AlphaSetId ::= INTEGER(0..maxNrofP0-PUSCH-AlphaSets-1) P0-PUSCH-AlphaSetIdExt ::= INTEGER(4..maxNrofP0-PUSCH-AlphaSetsExt-1)

-   -   2. The UE needs to dynamically perform measurement through the        MAC CE updating the mapping between the path loss RSs and the        SRIs, and a path loss RS may be indicated by an SRI. A specific        MAC CE structure and operation method will be described in        detail below in the disclosure.    -   3. A specific path loss RS used for PUSCH transmission (based on        a codebook or a non-codebook) may be indicated via an SRI in DCI        format 0_1, which is for specifying one path loss RS that is        actually applied although the UE measures up to four path loss        RSs in phases 1 and 2.

Referring to FIG. 9 , as in phase 1, 940, 945, 950, and 955 indicateconfigurations of up to 64 path loss RSs that can be configuredparticularly through PUSCH-PathlossReferenceRS in PUSCH-Config of theRRC message. As illustrated, 901, 903, 905, 907, 909, 911, 913, and 915indicate a mapping relationship of path loss RSs associated with SRIsthat can be initially configured particularly throughSRI-PUSCH-PowerControl in PUSCH-Config of the RRC message. Mappingbetween the SRIs and the path loss RSs configured through the RRCmessage is configured, and one path loss RS used for actual PUSCHtransmission is indicated via an SRI through DCI. There is norestriction on mapping between the SRIs and the path loss RSs exceptthat up to four path loss RSs can be configured. Subsequently, a pathloss RS to be measured may be updated through the MAC CE for updatingmapping between the path loss RSs and the SRIs, and a relationshipbetween the path loss RSs and the SRIs is indicated by 921, 923, 925,927, 929, 931, 933, and 935.

A specific example is illustrated below. Eight pieces of SRI mappinginformation may be initially configured through the RRC message, each ofwhich has a mapping relationship with a path loss RS as follows.

-   -   SRI #1 is associated with path loss RS #1    -   SRI #2 is associated with path loss RS #1    -   SRI #3 is associated with path loss RS #2    -   SRI #4 is associated with path loss RS #2    -   SRI #5 is associated with path loss RS #3    -   SRI #6 is associated with path loss RS #3    -   SRI #7 is associated with path loss RS #4    -   SRI #8 is associated with path loss RS #4

Subsequently, the mapping relationship between the SRIs and the pathloss RSs is updated as follows by receiving the MAC CE.

-   -   SRI #1 is associated with path loss RS #11    -   SRI #2 is associated with path loss RS #11    -   SRI #3 is associated with path loss RS #21    -   SRI #4 is associated with path loss RS #21    -   SRI #5 is associated with path loss RS #33    -   SRI #6 is associated with path loss RS #33    -   SRI #7 is associated with path loss RS #44    -   SRI #8 is associated with path loss RS #44

Introducing dynamic updating of mapping between the SRIs and the pathloss RSs described above may replace an existing procedure of updatingan RRC configuration, making it possible to change configurationinformation with a low delay.

FIG. 10 illustrates an overall UE operation for a measurement resourcetype, dynamic mapping updating, and a valid resource indication for aplurality of path loss RSs configured in a PUSCH according to anembodiment of the disclosure.

Referring to FIG. 10 , a UE in an RRC-connected state may receive PUSCHconfiguration information in operation 1005, and the configurationinformation may provide path loss RS configuration information requiredto determine signal strength and power for PUSCH transmission andconfiguration information about an association between an SRI and a pathloss RS. In particular, information about a path loss RS associated withan SRI that can be initially configured particularly throughSRI-PUSCH-PowerControl in PUSCH-Config of an RRC message may beconfigured. Mapping between SRIs and path loss RSs configured throughthe RRC message may be configured, and one path loss RS used for actualPUSCH transmission may be indicated via an SRI through DCI. There is norestriction on mapping between the SRIs and the path loss RSs exceptthat up to four path loss RSs can be configured. Specific configurationinformation and a specific operation have been described in detail withreference to FIG. 9 .

In operation 1010, the UE may perform L3 measurement on up to four pathloss RS resources requiring initial measurement, configured in operation1005, and may store and manage measurement values. In operation 1015,the UE may receive a path loss RS update MAC CE for updating the mappingbetween the path loss RSs and the SRIs through a base station and mayupdate and manage information about the relationship between the pathloss RSs and the SRIs using information indicated by the MAC CE. Inoperation 1015, the UE may measure a path loss RS according to aprevious mapping rule for a specific time (transition time), and maymeasure and reflect a path loss RS configured in a newly changed mappingrule after the predetermined specific time (transition time). This isbecause path loss RS measurement is based on L3 measurement, and thus ameasurement value cannot be changed immediately through the MAC CE, andthe average value needs to be calculated by applying previousmeasurement values. A specific structure and information of the MAC CEand a specific operation will be described in more detail in thefollowing embodiments. In particular, two methods may be considered inrelation to an MAC CE structure for path loss RS updating.

-   -   First MAC CE mapping method for path loss RS updating (described        in FIG. 11 ): Method of indicating a plurality of SRI indexes to        which one path loss RS is applied    -   Second MAC CE mapping method for path loss RS updating        (described in FIG. 12 ): Method of indicating SRI indexes to        which a plurality of path loss RSs is respectively applied

In these two methods, a condition is also required that the total sum ofpath loss RSs associated with an SRI is limited to four. This is becausethe UE can measure and manage only up to four path loss RSs. That is, inoperation 1020, the UE may measure and manage up to four path loss RSsbased on the information updated in operation 1015.

In operation 1025, the UE may receive scheduling for uplink transmission(PUSCH) from the base station through DCI, and the control informationmay indicate not only scheduling resource information but also aspecific path loss RS applied to calculation of signal strength andpower for the transmission. That is, the path loss RS mapped with an SRIof the DCI may be indicated, and the UE may measure a corresponding pathloss RS resource and may calculate path loss. In operation 1030, the UEmay determine power for a PUSCH transmission signal considering the passloss.

FIG. 11 illustrates a first MAC CE and a first mapping method fordynamic updating of a path loss RS requiring measurement according to anembodiment of the disclosure.

Referring to FIG. 11 , a plurality of SRI indexes to which one path lossRS is applied. To indicate updating of a plurality of path loss RSs, aplurality of MAC CEs needs to be transmitted. A new downlink MAC CEwhich has not previously existed needs to be introduced, and a new LCIDmay be allocated. The disclosure proposes option 1 of indicating a pathloss RS in a bitmap and option 2 of directly indicating a path loss RSindex, and specific MAC CE structures and related fields may be asfollows.

-   -   1. Option 1: Method of indicating a path loss RS index based on        a bitmap        -   Supplementary uplink (SUL) indicator 1101: Indicates an            uplink type, 1 bit        -   Serving cell ID 1103: Serving cell index, 5 bits        -   Bandwidth part (BWP) ID 1105: BWP index, 2 bits, A specific            group index indicated by an RRC configuration may be            indicated instead of the serving cell index and the BWP            index        -   Indicator indicating whether there is a plurality of SRI IDs            (C1) 1107 and 1115: Indicates whether there is an additional            SRI ID associated with a path loss RS 1123 subsequently            indicated through 1 bit        -   SRI ID 1109 and 1117: Index of an SRI associated with a path            loss RS, 4 bits        -   Closed loop index (CLId) 1111 and 1119: Optionally included            or may not be included, Used to identify a closed loop            index, 1 bit        -   Alpha value index (AlphaSetId) 1113 and 1121: Optionally            included or may not be included, Forwards an index            corresponding to a specific alpha value for transmission            power adjustment, 5 bits        -   Path loss RS index 1123: Indicates the index of one path            loss RS among up to 64 path loss RSs in a bitmap, 8 bytes,            only one bit can be set to 1    -   2. Option 2: Method of directly indicating a path loss RS index        -   SUL (supplementary uplink) indicator 1151: Indicates an            uplink type, 1 bit        -   Serving cell ID 1153: Serving cell index, 5 bits        -   BWP ID 1155: BWP index, 2 bits, A specific group index            indicated by an RRC configuration may be indicated instead            of the serving cell index and the BWP index        -   Reserved bit 1157        -   Path loss RS index 1159: Path loss RS index, 5 bits,            Indicates a path loss resource associated with an SRI            signaled below        -   Indicator indicating whether there is a plurality of SRI IDs            (C1) 1161 and 1169: Indicates whether there is an additional            SRI ID associated with a path loss RS 1159 indicated by a            corresponding MAC CE through 1 bit        -   SRI ID 1163 and 1171: Index of an SRI associated with a path            loss RS, 4 bits        -   Closed loop index (CLId) 1165 and 1173: Optionally included            or may not be included, Used to identify a closed loop            index, 1 bit        -   Alpha value index (AlphaSetId) 1167 and 1175: Optionally            included or may not be included, Forwards an index            corresponding to a specific alpha value for transmission            power adjustment, 5 bits

FIG. 12 illustrates a second MAC CE and a second mapping method fordynamic updating of a path loss RS requiring measurement according to anembodiment of the disclosure.

Referring to FIG. 12 , is characterized in that mapping informationabout a plurality of SRI indexes to which one path loss RS is appliedindicates that a plurality of sets is simultaneously updated. That is,to indicate updating of a plurality of path loss RSs, rather thanrequiring transmission of a plurality of MAC CEs as in FIG. 11 , aplurality of path loss RSs is indicated through one MAC CE and mappinginformation about an SRI associated with the path loss RSs is provided.A new downlink MAC CE which has not previously existed needs to beintroduced, and a new LCID may be allocated. The disclosure proposesoption 1 of indicating a path loss RS in a bitmap and option 2 ofdirectly indicating a path loss RS index, and specific MAC CE structuresand related fields may be as follows.

-   -   1. Option 1: Method of indicating a path loss RS index based on        a bitmap        -   SUL (supplementary uplink) indicator 1201: Indicates an            uplink type, 1 bit        -   Serving cell ID 1203: Serving cell index, 5 bits        -   BWP ID 1205: BWP index, 2 bits, A specific group index            indicated by an RRC configuration may be indicated instead            of the serving cell index and the BWP index.        -   Indicator indicating whether there is a plurality of SRI IDs            (C1) 1207, 1215, 1225, and 1233: Indicates whether there is            an additional SRI ID associated with a path loss RS 1223            subsequently indicated through 1 bit        -   SRI ID 1209, 1217, 1227, and 1235: Index of an SRI            associated with a path loss RS, 4 bits        -   Closed loop index (CLId) 1211, 1219, 1229, and 1237:            Optionally included or may not be included, Used to identify            a closed loop index, 1 bit        -   Alpha value index (AlphaSetId) 1213, 1221, 1231, and 1239:            Optionally included or may not be included, Forwards an            index corresponding to a specific alpha value for            transmission power adjustment, 5 bits        -   Path loss RS index 1223 and 1241: Indicates the index of one            path loss RS among up to 64 path loss RSs in a bitmap, 8            bytes, only one bit can be set to 1    -   2. Option 2: Method of directly indicating a path loss RS index        -   Supplementary uplink (SUL) indicator 1251: Indicates an            uplink type, 1 bit        -   Serving cell ID 1253: Serving cell index, 5 bits        -   BWP ID 1255: BWP index, 2 bits, A specific group index            indicated by an RRC configuration may be indicated instead            of the serving cell index and the BWP index        -   Indicator for updating of a plurality of path loss RSs (C2)            1257 and 1277: Indicates that there is additional mapping            information about one path loss RS and an SRI, 1 bit        -   Path loss RS index 1259: Path loss RS index, 5 bits,            Indicates a path loss resource associated with an SRI            signaled below        -   Indicator indicating whether there is a plurality of SRI IDs            (C1) 1261, 1269, 1281, and 1289: Indicates whether there is            an additional SRI ID associated with a path loss RS 1159            indicated by a corresponding MAC CE through 1 bit        -   SRI ID 1263, 1271, 1283, and 1291: Index of an SRI            associated with a path loss RS, 4 bits        -   Closed loop index (CLId) 1265, 1273, 1285, and 1293:            Optionally included or may not be included, Used to identify            a closed loop index, 1 bit        -   Alpha value index (AlphaSetId) 1267, 1275, 1287, and 1295:            Optionally included or may not be included, Forwards an            index corresponding to a specific alpha value for            transmission power adjustment, 5 bits

FIG. 13 illustrates an overall UE operation for a measurement resourcetype and dynamic resource indication for a path loss RS configured inSRS transmission according to an embodiment of the disclosure.

Referring to FIG. 13 , a UE in an RRC-connected state may receiveconfiguration information about an SRS resource in operation 1305, andthe configuration information may provide path loss RS configurationinformation required to determine signal strength and power for SRSresource transmission. In particular, path loss RS configurationinformation applied to one SRS resource set may be provided to the UEthrough SRS-ResourceSet in SRS-Config of an RRC message. Although onepath loss RS is configured via RRC, up to 64 resources may beconfigured. Table 4 relates to a path loss RS configuration method forSRS transmission based on Rel-15, and a plurality of path loss RSconfigurations may be subsequently added in SRS-ResourceSet in anextended manner. Further, it is necessary to indicate an initial pathloss resource requiring initial measurement. In one example, apreviously used field may be used as an initial value, and an extendedpath loss RS configuration may be used for dynamic resource updatingthrough a MAC CE.

TABLE 4 SRS-ResourceSet ::= SEQUENCE {  srs-ResourceSetIdSRS-ResourceSetId,  srs-ResourceIdList SEQUENCE(SIZE(1..maxNrofSRS-ResourcesPerSet)) OF SRS-ResourceId OPTIONAL, --Cond Setup  resourceType CHOICE {   aperiodic SEQUENCE {   aperiodicSRS-ResourceTrigger INTEGER (1..maxNrofSRS-TriggerStates-1),    csi-RS NZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebook   slotOffset INTEGER (1..32) OPTIONAL, -- Need S    ...,    [[   aperiodicSRS-ResourceTriggerList-v1530 SEQUENCE (SIZE(1..maxNrofSRS-TriggerStates-2))     OF INTEGER (1..maxNrofSRS-TriggerStates-1)OPTIONAL -- Need M    ]]   },   semi-persistent SEQUENCE {   associatedCSI-RS NZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebook   ...   },   periodic SEQUENCE {    associatedCSI-RSNZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebook    ...   }  }, usage ENUMERATED {beamManagement, codebook, nonCodebook,antennaSwitching},  alpha Alpha OPTIONAL, -- Need S  p0 INTEGER(−202..24) OPTIONAL, - - Cond Setup  pathlossReferenceRS CHOICE {  ssb-Index SSB-Index,   csi-RS-Index NZP-CSI-RS-ResourceId  } OPTIONAL,-- Need M  srs-PowerControlAdjustmentStates ENUMERATED { sameAsFci2,separateClosedLoop} OPTIONAL, -- Need S  ... } SRS-ResourceSetId ::=INTEGER (0..maxNrofSRS-ResourceSets-1)

The UE may perform L3 measurement on the path loss RS resource requiringinitial measurement, configured in operation 1305, and may store andmanage measurement values. In operation 1310, the UE receives an MAC CEfor actually measuring a plurality of path loss RSs configured inoperation 1305 and indicating a resource which needs to be applied froma base station. A specific MAC CE structure and a specific operationwill be described in FIG. 14 . In operation 1315, the UE may measure apath loss RS resource indicated through the received MAC CE, maycalculate path loss, and may determine power for an SRS transmissionsignal in view of the path loss.

FIG. 14 illustrates an MAC CE and a mapping method for dynamic updatingof a path loss RS requiring measurement according to an embodiment ofthe disclosure.

Referring to FIG. 14 , a UE may configure a plurality of path loss RSresources in SRS-Config (specifically, an SRS-ResourceSet configuration)of an RRC message. Further, it is necessary to indicate an initial pathloss resource requiring initial measurement. In one example, apreviously used field may be used as an initial value, and an extendedpath loss RS configuration may be used for dynamic resource updatingthrough an MAC CE. Subsequently, when it is necessary to update aresource for measuring a path loss RS which is applied to SRStransmission and is needed to calculate transmission power, the resourcemay be updated to one of a plurality of path loss RSs through the MACCE. The structure illustrated in FIG. 14 may be used.

-   -   Serving cell ID including SRS resource set 1405: 5 bits    -   BWP ID including SRS resource set ID 1410: 2 bits    -   SUL indicator 1415: 1 bit    -   SRS resource set ID 1420: 4 bits    -   Path loss RS index 1425: 6 bits, path loss RS resource        information indicating dynamic change to the UE

FIG. 15 illustrates the overall operation of a measurement andapplication of a path loss RS for PUSCH and SRS transmission accordingto an embodiment of the disclosure.

Referring to FIG. 15 , a UE 1501 may camp on a specific base station1502, in operation 1505, and may perform RRC connection setup with acorresponding serving cell, in operation 1510. The UE 1501 may performdata transmission and reception with the base station 1502 in operation1515, and the base station 1502 may provide configuration informationfor path loss calculation which the UE 1501 needs to consider for uplinktransmission through an RRC configuration, in operation 1520. Inoperation 1520, the UE 1501 may receive PUSCH configuration informationand SRS configuration information. The PUSCH configuration informationmay include a plurality of pieces (up to 64 pieces) of path loss RSconfiguration information required to determine signal strength andpower for PUSCH transmission and configuration information about anassociation between an SRI and a path loss RS, and the SRS configurationinformation may include a plurality of pieces (up to 64 pieces) of pathloss RS configuration information for SRS transmission configured perSRS-ResourceSet. In operation 1520, the UE 1501 may perform L3measurement on up to four path loss RS resources requiring initialmeasurement configured for a PUSCH and an initial path loss resourceconfigured for an SRS, and may store and manage measurement values.

In operation 1525, the UE 1501 may receive a path loss RS update MAC CEfor updating mapping between the path loss RS and the SRI through thebase station 1502 and may update and manage the mapping usinginformation indicated by the MAC CE. In operation 1530, the UE 1501 mayreceive scheduling for uplink transmission (PUSCH) from the base station1502 through DCI, and the control information may include not onlyscheduling resource information but also information indicating aspecific path loss RS applied to calculation of signal strength andpower for the transmission. That is, the path loss RS mapped with an SRIof the DCI may be indicated, and the UE 1501 may measure a correspondingpath loss RS resource and may calculate path loss. In operation 1535,the UE 1501 may determine power for a PUSCH transmission signalconsidering the pass loss and may perform transmission.

The UE 1501 may perform SRS transmission according to a configured SRStransmission configuration while performing the foregoing operation, inwhich the UE 1501 may determine transmission power based on a path lossRS indicated through an initial RRC configuration. In operation 1540,the UE 1501 may receive an MAC CE indicating a path loss resource whichneeds to be measured and applied in actual SRS transmission from thebase station 1502. In operation 1545, the UE 1501 may measure a pathloss RS resource indicated by the received MAC CE, may calculate pathloss, and may determine power for an SRS transmission signal in view ofthe pass loss.

FIG. 16 illustrates an overall operation of a base station to which thedisclosure is applied according to an embodiment of the disclosure.

Referring to FIG. 16 , the base station establishes connection setupwith a UE, in operation 1605, and requests and receives a capability ofthe UE, in operation 1610. In operation 1610, the base station maydetermine whether the UE has a dynamic path loss RS updating capabilityaccording to the capability of the UE. Subsequently, in operation 1615,the base station may provide RRC configuration information to the UE inview of the capability of the UE. In operation 1615, the base stationmay provide a plurality of path loss RS configurations to the UE via aPUSCH configuration and an SRS configuration information. For a UE witha dynamic path loss RS updating capability, the base station may updateinformation about mapping between a path loss RS and an SRI applicableto PUSCH transmission through an MAC CE, in operation 1620. In operation1625, the base station may forward to the UE an indication for a pathloss RS which needs to be applied to actual PUSCH and SRS transmissionin association with an SRI index via DCI or may indicate to the UE aspecific path loss RS index through an MAC CE. In operation 1630, thebase station may receive an uplink signal transmitted from the UE.

According to the disclosure, in order to improve an MIMO operation in anext-generation mobile communication system, it is generally possible toupdate/indicate a beam (spatial relation) through a single MAC CE for aPUCCH resource in a specific bandwidth part (BWP) within one servingcell in an operation of a UE configuring and activating beam information(spatial relation) used for PUCCH transmission. However, since aplurality of PUCCH resources may be configured in one serving cell and aBWP, a plurality of MAC CE transmissions is required to update beaminformation about all the configured PUCCH resources, thus causing anincrease in signaling and latency time. Therefore, the disclosureproposes a method in which a plurality of PUCCH resources is configuredand pieces of information about beams for transmitting the plurality ofPUCCH resources are simultaneously updated.

FIG. 17 illustrates a structure of a next-generation mobilecommunication system and a scenario in which a PUCCH resourceconfiguration and a beam activation operation are applied according toan embodiment of the disclosure.

Referring to FIG. 17 , there may be a plurality of cells served by NRgNBs operating based on a beam. A UE 1715 being connected to a specificcell (cell 1) 1705 may receive a configuration of a different servingcell (cell 2) 1710. Accordingly, the UE 1715 can transmit and receivedata to and from a plurality of cells through CA. In an existing NRsystem, a physical downlink control channel (PDCCH) configuration and aphysical downlink shared channel (PDSCH) configuration may be providedper serving cell and BWP through an RRC control signal, therebyproviding configuration information for reception of a downlink controlsignal and a data signal and related reception beam configurationinformation may be provided (1720 and 1725). In addition, PUCCH-Configmay be provided per serving cell and BWP through the RRC control signal,and a PUCCH resource and a related transmission beam may besimultaneously configured according to the configuration (1730 and1735). Currently, in one cell group, one PUCCH SCell may be furtherconfigured in addition to a primary cell (PCell)/primary-secondary cell(PSCell). A method for configuring a PUCCH resource in a PUCCH resourceconfiguration operation through an RRC control message is as follows.

-   -   PUCCH resource sets: A unit in which PUCCH resources having the        same payload are grouped. PUCCH resources existing in one PUCCH        resource set have the same payload size. Up to four PUCCH        resource sets may be configured per BWP.    -   PUCCH resources: Configuration information about an actual PUCCH        resource is included, and up to 32 PUCCH resources may be        configured per PUCCH resource set. The index of all PUCCH        resources is 128    -   Spatial relations info: Table 5 below shows information about        beams though which the PUCCH resources are actually transmitted,        and one beam may be selected from among a synchronization signal        block (SSB), a channel state information reference signal        (CSI-RS), and a sounding reference signals (SRS). Up to eight        pieces of beam information may be configured per BWP, and the        number of corresponding beams may be increased to 64 from 8 in        Rel-16

TABLE 5 PUCCH-SpatialRelationInfo ::= SEQUENCE { pucch-SpatialRelationInfoId PUCCH-SpatialRelationInfoId,  servingCellId  ServCellIndex OPTIONAL, -- Need S  referenceSignal   CHOICE { ssb-Index  SSB-Index,  csi-RS-Index   NZP-CSI-RS-ResourceId,  srsSEQUENCE {    resource SRS-ResourceId,    uplinkBWP  BWP-Id   }  }, pucch-PathlossReferenceRS-Id  PUCCH-PathlossReferenceRS-Id, p0-PUCCH-Id   P0-PUCCH-Id,  closedLoopIndex    ENUMERATED { i0, i1 } }PUCCH-SpatialRelationInfoId ::= INTEGER (1..maxNrofSpatialRelationInfos)

Based on the RRC configuration information about the PUCCH resource, theUE may transmit a PUCCH/ACK/NACK signal in response to a downlinksignal. In addition, initial beam information associated with each PUCCHresource in the above operation may be beam information used in aninitial RRC connection procedure (SSB in an initial RACH operation), andan MAC CE may be subsequently used to update beam information associatedwith a specific PUCCH resource. That is, a PUCCH spatial relationactivation/deactivation MAC CE is used and has the following structure.

-   -   Reserved bits (included for byte alignment) 1745 and 1760    -   Serving Cell ID (5 bits) 1750    -   BWP ID (2 bits) 1755    -   PUCCH resource ID (7 bits) 1765    -   Spatial relation bitmap (1 bit, only one of up to eight bitmaps        is activated) 1770

This operation indicates a beam through which a PUCCH resource in aserving cell and a BWP indicated by the MAC CE is transmitted. Whenreceiving the MAC CE, the UE may update and apply information about abeam associated with the related PUCCH resource. As described above,PUCCH configuration information per BWP may be provided, and up to 128PUCCH resources may be configured. Thus, updating through 128 MAC CEsmay be required to update beam information about 128 configured PUCCHresources at worst, which increases latency in the correspondingoperation and causes significant signaling overhead.

FIG. 18 illustrates an operation of simultaneously updating transmissionbeams by grouping a plurality of PUCCH resources configured through aplurality of serving cells and a BWP in an NR system according to anembodiment of the disclosure.

As described in FIG. 17 , the NR system is designed to enable datatransmission/reception between a UE and a base station using a beam withdirectivity. Currently, only activation/deactivation of a beam(transmission configuration indicator (TCI) state or PUCCH spatialrelation) in a specific BWP in one serving cell is possible. In thedisclosure, a method in which a plurality of PUCCH resources isconfigured as a group and beam updating operations for the plurality ofPUCCH resources are simultaneously supported is considered. Thefollowing specific scenarios are applicable.

-   -   RRC configuration scenario 1: It is possible to configure a        group for a plurality of serving cells and a plurality of PUCCH        resources configured in a plurality of BWPs of the cells and to        simultaneously update pieces of beam information applied to        transmission (group configuration per cell group)    -   RRC configuration scenario 2: It is possible to configure a        group for a single serving cell and a plurality of PUCCH        resources configured in a plurality of BWPs of the cell and to        simultaneously update pieces of beam information applied to        transmission (group configuration per cell)    -   RRC configuration scenario 3: It is possible to configure a        group for a single serving cell and a plurality of PUCCH        resources configured in a single BWP of the cell and to        simultaneously update pieces of beam information applied to        transmission (group configuration per BWP)

According to the disclosure, it is possible to reduce latency time in abeam updating operation for a PUCCH resource and to reduce signalingoverhead for the beam updating operation. The above three scenarios aredifferent in level at which a group is configured for a plurality ofPUCCH resources, and the groups may be configured and operated in cellgroup, cell, and BWP levels.

Referring to FIG. 18 , a UE 1801 in an idle (RRC_IDLE) mode may searchfor a suitable cell, may camp on a corresponding base station, inoperation 1805, and may then access the base station and a PCell 1802when data to be transmitted is generated, in operation 1810. In the idlemode, the UE is not connected to a network for power saving and thuscannot transmit data. The UE needs to transition to a connected(RRC_CONNECTED) mode for data transmission. The UE camping means thatthe UE stays in the cell and receives a paging message to determinewhether downlink data is transmitted. When the UE succeeds in accessingthe base station and the PCell 1802, the UE changes a state thereof tothe connected (RRC_CONNECTED) mode, and can perform data transmissionand reception with the base station in the connected mode, in operation1815.

In operation 1820, the base station may transmit configurationinformation (ServingCellConfig) for configuring a plurality of servingcells and BWPs to the UE through an RRC message in the RRC-connectedstate. The RRC message may include configuration information forreception through a PDCCH and a PDSCH (PDCCH-Config and PDSCH-Config)and configuration information for PUCCH transmission (PUCCH-Config).Specifically, the RRC message may include a BWP configuration(BWP-Uplink and BWP-Downlink), a CORESET configuration, a scramblingconfiguration, a TCI state (TCI-State in PDSCH-Config) configuration,and the like. For example, the TCI state configuration may be providedper downlink BWP of each serving cell and may be individually includedin PDCCH-Config and PDSCH-Config, and a beam configuration for PUCCHresource transmission may be included in PUCCH-Config. In the PUCCHconfiguration, a PUCCH resource, a PUCCH resource set, spatial relationinformation, and the like may be configured, and details of theconfiguration are as described in FIG. 17 . Particularly, in the aboveoperation, the number of pieces of spatial relation information for aPUCCH resource may be increased from existing 8 to 64, which means thata beam resolution for PUCCH resource transmission can be furtherincreased.

According to the disclosure, in operation 1820, for example, in order topre-configure a plurality of PUCCH resource groups applicable to thesame transmission beam in an RRC configuration, a plurality of PUCCHresources or PUCCH resource sets applicable to the same transmissionbeam according to application of the foregoing three scenario may beconfigured as a single group. Alternatively, a current PUCCH resourceset may serve as a PUCCH resource group for performing simultaneous beamupdating. The PUCCH resource group may be configured and operated in acell group, cell, or BWP level according to a scenario. In thisoperation, information about an applied beam for an initial PUCCHresource group may be configured through the RRC message. In this case,PUCCH transmission may be performed for the PUCCH resource group inassociation with preset initial beam information until a beaminformation update is indicated through a separate MAC CE.

-   -   RRC configuration scenario 1: A plurality of serving cells and a        plurality of PUCCH resources existing in a BWP may be configured        as a single group/list in CellGroupConfig (one entry in the        group is configured as serving cell ID+BWP ID+PUCCH resource ID        or PUCCH resource set ID)    -   RRC configuration scenario 2: A plurality of PUCCH resources        existing in a plurality of BWPs of a serving cell may be        configured as a single group/list in ServingCellConfig (one        entry in the group is configured as BWP ID+PUCCH resource ID or        PUCCH resource set ID)    -   RRC configuration scenario 3: A plurality of PUCCH resources        existing in a serving cell and a BWP may be configured as a        single group/list in PUCCH-Config of a BWP (one entry in the        group is configured as PUCCH resource ID or PUCCH resource set        ID)

Table 6 illustrates an RRC message that can be transmitted when RRCconfiguration scenario 3 is applied.

TABLE 6 PUCCH-Config ::= SEQUENCE {  resourceSetToAddModList SEQUENCE(SIZE (1..maxNrofPUCCH-ResourceSets)) OF PUCCH-ResourceSet OPTIONAL, --Need N  resourceSetToReleaseList SEQUENCE (SIZE(1..maxNrofPUCCH-ResourceSets)) OF PUCCH-ResourceSetIdOPTIONAL, -- NeedN  resourceToAddModList SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OFPUCCH-Resource OPTIONAL, -- Need N  resourceToReleaseList SEQUENCE (SIZE(1..maxNrofPUCCH-Resources)) OF PUCCH-ResourceId OPTIONAL, -- Need N format1 SetupRelease { PUCCH-FormatConfig } OPTIONAL, -- Need M format2 SetupRelease { PUCCH-FormatConfig } OPTIONAL, -- Need M format3 SetupRelease { PUCCH-FormatConfig } OPTIONAL, -- Need M format4 SetupRelease { PUCCH-FormatConfig } OPTIONAL, -- Need M schedulingRequestResourceToAddModList SEQUENCE (SIZE (1..maxNrofSR-Resources)) OFSchedulingRequestResourceConfig      OPTIONAL, -- Need N schedulingRequestResourceToReleaseList SEQUENCE (SIZE (1..maxNrofSR-Resources)) OFSchedulingRequestResourceId      OPTIONAL, -- Need N multi-CSI-PUCCH-ResourceList SEQUENCE (SIZE (1..2)) OF PUCCH-ResourceIdOPTIONAL, -- Need M  dl-DataToUL-ACK SEQUENCE (SIZE (1..8)) OFINTEGER(0..15) OPTIONAL, -- Need M  spatialRelationInfoToAddModList SEQUENCE(SIZE (1..maxNrofSpatialRelationInfos)) OF PUCCH-SpatialRelationInfo     OPTIONAL, -- Need N  spatialRelationInfoToReleaseList SEQUENCE(SIZE (1..maxNrofSpatialRelationInfos)) OF PUCCH-SpatialRelationInfoId     OPTIONAL, -- Need N  pucch-PowerControl PUCCH-PowerControlOPTIONAL, -- Need M  ...,  [[ spatialRelationInfoToAddModListExt-r16SEQUENCE (SIZE (1..maxNrofSpatialRelationInfosExt)) OFPUCCH-SpatialRelationInfo-r16 OPTIONAL, -- Need N  spatialRelationInfoToReleaseListExt-r16 SEQUENCE (SIZE(1..maxNrofSpatialRelationInfosExt)) OF PUCCH-SpatialRelationInfoId-r16OPTIONAL, -- Need N resourceGroupToAddModList-r16 SEQUENCE (SIZE(1..maxNrofPUCCH- ResourceGroup)) OF PUCCH-ResourceGroup OPTIONAL, --Need N   resourceGroupToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceGroup)) OF PUCCH-ResourceGroupId OPTIONAL, -- Need N ]] }PUCCH-ResourceGroup ::= SEQUENCE {  pucch-ResourceGroupIdPUCCH-ResourceGroupId,  pucch-resourceList SEQUENCE (SIZE(1..maxNrofPUCCH-Resources)) OF PUCCH-ResourceId OPTIONAL, -- Need N spatialRelationInfo-r16 PUCCH-SpatialRelationInfoId-r16 OPTIONAL, --Need R } PUCCH-ResourceGroupId::= INTEGER (0..maxNrofPUCCH-ResourceGroup-1) maxNrofSpatialRelationInfos INTEGER ::= 8maxNrofSpatialRelationInfosExt INTEGER ::= 56PUCCH-SpatialRelationInfo-r16 ::= SEQUENCE { pucch-SpatialRelationInfoId-r16 PUCCH-SpatialRelationInfoId-r16, servingCellId ServCellIndex OPTIONAL, -- Need S  referenceSignal CHOICE{   ssb-Index SSB-Index,   csi-RS-Index NZP-CSI-RS-ResourceId,   srsSEQUENCE {     resource SRS-ResourceId,     uplinkBWP BWP-Id    }  }, pucch-PathlossReferenceRS-Id PUCCH-PathlossReferenceRS-Id,  p0-PUCCH-IdP0-PUCCH-Id,  closedLoopIndex ENUMERATED { i0, i1 } }PUCCH-SpatialRelationInfoId-r16 ::= INTEGER(0..maxNrofSpatialRelationInfos-1- r16)maxNrofSpatialRelationInfos-1-r16 ::= 63 maxNrofSpatialRelationInfos-r16::= 64

Alternatively, an applied beam-updating operation for a plurality ofPUCCH resources may be supported via an MAC rather than pre-configuringa plurality of PUCCH resource groups applicable to the same transmissionbeam in an RRC configuration as in operation 1820. In this case, thePUCCH resource group through the RRC configuration described above maybe omitted. A specific MAC CE structure and operation according to anapplied scenario will be described in the following embodiments.

In operation 1825, the base station transmits an MAC CE forindicating/updating a transmission beam for a PUCCH resource configuredvia the RRC configuration information. In the disclosure, the MAC CEused in this operation may be an MAC CE indicating simultaneoustransmission beam updating for a plurality of PUCCH resources. The typeand structure of the MAC CE applied in this operation may vary accordingto embodiments and may be classified as follows.

-   -   When an RRC-based method is used: A group ID and applied beam        information may be provided based on PUCCH resource group        information configured in an RRC control message. A specific        structure will be mentioned in an embodiment below    -   When a MAC CE-only method is used: The MAC CE includes the IDs        of all PUCCH resource to which simultaneous beam updating is        applied. A specific structure will be mentioned in an embodiment        below

According to the disclosure, simultaneous beam updating for a pluralityof PUCCH resources may be possible in operation 1820, operation 1825. Inoperation 1830, the base station indicates downlink scheduling anddownlink control information. The following embodiments provide specificmethod for updating. In operation 1835, data transmission and receptionto which corresponding transmission and reception resources are appliedmay be performed through a downlink beam (TCI state) and an uplink beam(PUCCH resource transmission beam) indicated in operation 1825 andoperation 1830. For example, the UE performs uplink data receptionthrough a beam configured for communication with the base station. Inparticular, ACK/NACK transmission may be performed through a PUCCHresource.

In operation 1840, the base station may further transmit an MAC CE inorder to update the previously transmitted MAC CE and may updateactivated and deactivated beams using the MAC CE. In the disclosure,operation 1840 is intended to perform updating of a beam for anindividual PUCCH resource rather than simultaneous beam updating for aplurality of PUCCH resources. For example, simultaneous beam updatingfor a plurality of PUCCH resources may be activated in operation 1825,and beam updating for an individual PUCCH resource may be performed, inoperation 1840, and communicate using the updated beam, in operation1845.

The foregoing operation of configuring PUCCH resource as a group andsimultaneously updating beams may update a beam by specifying aconfigured group ID or a specific group. Further, the foregoingoperation may also support an operation of simultaneously updating beamsfor all additionally configured groups, which may be indicated by theMAC CE used in operation 1825, and the UE receiving the MAC CE mayupdate beams for PUCCH resources for all the configured groups to anindicated beam. Alternatively, an additional group including all thegroups may be configured in the RRC configuration operation of 1820. Forexample, PUCCH resources configured as a group may be configured inanother group at the same time. A specific MAC CE structure and fieldwill be described in a separate embodiment below.

The following embodiments propose specific methods in view of possibleoptions as methods for supporting simultaneous beam updating for PUCCHresources described above. In particular, a third embodiment discloses ascenario in which an RRC reconfiguration is used as a method forconfiguring a PUCCH resource group. A fourth embodiment discloses ascenario in which all information about PUCCH resources requiring beamupdating is included in a MAC CE. In addition, not only simultaneousbeam updating for a PUCCH resource group including a plurality of PUCCHresources but also beam updating for an existing individual PUCCHresource is supported, thereby supporting an efficient beam updatingoperation in addition to a reduction in signaling overhead and latencytime. An overall operation follows a flowchart illustrated in FIG. 18 ,and specific operations will be described in the following embodiments.

FIG. 19 illustrates a UE operation of configuring a PUCCH resource groupvia an RRC control message and applying simultaneous beam updating forthe PUCCH resource group through an MAC CE according to an embodiment ofthe disclosure.

Referring to FIG. 19 , in operation 1905, a UE in an RRC-connected stategenerates, stores, and transmits UE capability information to a basestation in response to a UE capability request message from the basestation. Particularly, in this operation, the UE capability informationincludes information about whether simultaneous beam updating for aplurality of PUCCH resources is supported. To indicate this information,two methods illustrated below may be used.

1. First Method for Transmitting UE Capability

A one-bit indicator is employed to indicate whether the UE supportssimultaneous beam updating for a plurality of PUCCH resources. When itis indicated that the UE supports a corresponding capability, the basestation may establish a corresponding configuration.

2. Second Method for Transmitting UE Capability

An indicator is included to indicate whether the UE supportssimultaneous beam updating for a plurality of PUCCH resources perspecific band or band combination supported by the UE. The base stationmay configure a corresponding function only for a BC including theindicator.

When the indicators are indicated as TRUE in the foregoing methods fortransmitting UE capability, the UE may equally apply the correspondingcapability to all BWPs belonging to a component carrier of a UE or a BCin which the corresponding function is configured. Alternatively, a UEcapability indicating that the corresponding capability is supported foreach BWP may be added.

In operation 1910, the base station may transmit configurationinformation (ServingCellConfig) for configuring a plurality of servingcells to the UE through an RRC message. The RRC message includesconfiguration information for reception through a PDCCH and a PDSCH(PDCCH-Config and PDSCH-Config), and a beam configuration for PUCCHresource transmission may be included in PUCCH-Config. Specifically, theRRC message may include a BWP configuration (BWP-Uplink andBWP-Downlink), a CORESET configuration, a scrambling configuration, aTCI state (TCI-State in PDSCH-Config) configuration, a set of a PUCCHresource and a PUCCH resource, spatial relation information, and thelike. For reference, regarding a spatial relation informationconfiguration, while up to eight pieces of spatial relation informationare supported, up to 64 pieces of spatial relation information may bedetermined and configured. Specifically, the TCI state configuration maybe provided per downlink BWP of each serving cell and may beindividually included in PDCCH-Config and PDSCH-Config, and a PUCCHresource configuration and a beam configuration for PUCCH resourcetransmission may also be included in PUCCH-Config. According to thethird embodiment, in operation 1910, a list of PUCCH resources or PUCCHresource sets to which simultaneous beam updating for a plurality ofPUCCH resources is applied is provided through the RRC message. The listis referred to as a PUCCH resource group in the disclosure, and thenumber of configured groups may be limited to four. However, this ismerely an example, and the limited number may be set to a greaternumber. In addition, serving cell information (e.g., a SCell ID) and BWPinformation (e.g., a BWP ID) to which the same beam configuration isapplied may also be configured along with a PUCCH resource ID or a PUCCHresource set ID in PUCCH-Config in which a PUCCH resource group isconfigured. A PUCCH resource ID or a PUCCH resource set ID includingcell information (e.g., a SCell ID) and BWP information (e.g., a BWP ID)to which the corresponding function is applied may be provided at aCellGroupConfig or ServingCellConFIG. level. In this case, a PUCCHresource group configuration needs to be equally applied to eachcorresponding cell group or serving cell and may be applied to allindicated serving cells and BWPs.

In operation 1915, the UE may receive a MAC CE indicating a beam forPUCCH resource transmission from the base station. In this operation,the UE may receive a MAC CE indicating beam activation for an existingindividual PUCCH resource or may receive a MAC CE indicatingsimultaneous beam updating for a plurality of newly defined PUCCHresources. A specific MAC CE structure will be described later.

In operation 1920, the UE analyzes the MAC CE received in operation 1915to determine which operation is indicated and then performs a relevantoperation. When the received MAC CE indicates simultaneous beam updatingfor a plurality of PUCCH resources (by allocating a new LCID orincluding indication information (e.g., a one-bit indicator) indicatingsimultaneous beam updating in an existing MAC CE field), the UE needs toapply beam information in the received MAC CE to a PUCCH resource groupmapped to a PUCCH resource group ID indicated by the MAC CE, inoperation 1925. A serving cell ID and a BWP ID indicated by the MAC CEin operation 1925 may be one serving cell and one BWP configured in acarrier and a BWP configured in operation 1910 and may be, for example,a PCell ID and an uplink active BWP ID. In operation 1930, the UE mayupdate a beam for a PUCCH resource belonging to the PUCCH resource groupindicated, in operation 1925. The UE may perform data transmission andreception through the configured beam in operation 1935, and may repeatoperation 1920 when receiving a beam-updating MAC CE associated with aPUCCH resource again.

When the MAC CE received by the UE indicates beam activation for anindividual PUCCH resource in operation 1920 (by allocating an existingLCID in an existing MAC CE, an existing MAC CE field not includingindication information indicating beam updating for a plurality ofserving cells and BWPs), the UE may apply relevant beam informationabout a PUCCH resource ID indicated by the received MAC CE, in operation1940, and may perform a corresponding operation, for example, may updatean associated beam, in operation 1945. In operation 1950, the UE mayperform data transmission and reception through the configured beam.When a beam-updating MAC CE associated with a PUCCH resource is receivedagain, operation 1920 may be repeated.

FIG. 20 illustrates an overall UE operation of supporting simultaneousbeam updating for a PUCCH resource group through an MAC CE according toan embodiment of the disclosure.

Referring to FIG. 20 , in operation 2005, a UE in an RRC-connected statemay generate, store, and transmit UE capability information to a basestation in response to a UE capability request message from the basestation. Particularly, in this operation, the UE capability informationmay include information about whether simultaneous beam updating for aplurality of PUCCH resources is supported. To indicate this information,two methods illustrated below may be used.

1. First Method for Transmitting UE Capability

A one-bit indicator is employed to indicate whether the UE supportssimultaneous beam updating for a plurality of PUCCH resources. When itis indicated that the UE supports a corresponding capability, the basestation may establish a corresponding configuration.

2. Second Method for Transmitting UE Capability

An indicator is included to indicate whether the UE supportssimultaneous beam updating for a plurality of PUCCH resources perspecific band or band combination supported by the UE. The base stationmay configure a corresponding function only for a BC including theindicator.

When the indicators are indicated as TRUE in the foregoing methods fortransmitting UE capability, the UE may equally apply the correspondingcapability to all BWPs belonging to a component carrier of a UE or a BCin which the corresponding function is configured. Alternatively, a UEcapability indicating that the corresponding capability is supported foreach BWP may be added.

In operation 2010, the base station may transmit configurationinformation (ServingCellConfig) for configuring a plurality of servingcells to the UE through an RRC message. The RRC message may includeconfiguration information for reception through a PDCCH and a PDSCH(PDCCH-Config and PDSCH-Config). Further, a beam configuration for PUCCHresource transmission may be included in PUCCH-Config. Specifically, theRRC message may include a BWP configuration (BWP-Uplink andBWP-Downlink), a CORESET configuration, a scrambling configuration, aTCI state (TCI-State in PDSCH-Config) configuration, a set of a PUCCHresource and a PUCCH resource, spatial relation information, and thelike. For reference, regarding a spatial relation informationconfiguration, while up to eight pieces of spatial relation informationare conventionally supported, up to 64 pieces of spatial relationinformation may be determined and configured. For example, the TCI stateconfiguration may be provided per downlink BWP of each serving cell andmay be individually included in PDCCH-Config and PDSCH-Config, and aPUCCH resource configuration and a beam configuration for PUCCH resourcetransmission may also be included in PUCCH-Config. According to thefourth embodiment, in operation 2010, a list of PUCCH resources or PUCCHresource sets to which simultaneous beam updating for a plurality ofPUCCH resources is applied is not provided through the RRC message. Thatis, according to the fourth embodiment, a PUCCH resource group is notspecified in an RRC configuration, but all PUCCH resources or PUCCHresource sets for which simultaneous beam updating is performed areindicated at once by an MAC CE transmitted, in operation 2015.

In operation 2015, the UE may receive an MAC CE indicating a beam forPUCCH resource transmission from the base station. In this operation,the UE may receive an MAC CE indicating beam activation for an existingindividual PUCCH resource or may receive an MAC CE indicatingsimultaneous beam updating for a plurality of newly defined PUCCHresources. A specific MAC CE structure will be described later.

In operation 2020, the UE analyzes the MAC CE received in operation 2015to determine which operation is indicated and then performs a relevantoperation. When the received MAC CE indicates simultaneous beam updatingfor a plurality of PUCCH resources (by allocating a new LCID orincluding indication information (e.g., a one-bit indicator) indicatingsimultaneous beam updating in an existing MAC CE field), the UE mayapply beam information in the received MAC CE to any PUCCH resource listindicated by the MAC CE, in operation 2025. For example, the MAC CE mayinclude a plurality of PUCCH resource IDs or PUCCH resource set IDs.Further, the operation includes a PUCCH resource belonging to adifferent serving cell or a different BWP, a plurality of sets each ofwhich includes a serving cell ID, a BWP ID, and a PUCCH resource ID maybe provided. A serving cell ID and a BWP ID indicated by the MAC CE inoperation 2025 may be one serving cell and one BWP configured in acarrier and a BWP configured in operation 2010 and may be, for example,a PCell ID and an uplink active BWP ID. In operation 2030, the UEupdates a beam for the PUCCH resource list indicated, in operation 2025.The UE may perform data transmission and reception through theconfigured beam, in operation 2035, and may repeat operation 2020 whenreceiving a beam-updating MAC CE associated with a PUCCH resource again.

When the MAC CE received by the UE indicates beam activation for anindividual PUCCH resource in operation 2020 (by allocating an existingLCID in an existing MAC CE, an existing MAC CE field not includingindication information indicating beam updating for a plurality ofserving cells and BWPs), the UE may apply relevant beam informationabout a PUCCH resource ID indicated by the received MAC CE, in operation2040, and may perform a corresponding operation, for example, may updatean associated beam, in operation 2045. The UE may perform datatransmission and reception through the configured beam, in operation2050, and may repeat operation 2020 when receiving a beam-updating MACCE associated with a PUCCH resource again.

FIG. 21 illustrates an MAC CE structure according to an embodiment ofthe disclosure.

FIG. 22 illustrates an MAC CE structure according to an embodiment ofthe disclosure.

In an embodiment of the disclosure, a PUCCH resource group is configuredvia an RRC control message, and simultaneous beam updating for the PUCCHresource group is applied through an MAC CE. Thus, the PUCCH resourcegroup is already configured in the RRC control message, and accordinglythe MAC CE may use this information. The MAC CE has specific structuresaccording to the following options.

-   -   Referring to FIG. 21 , a new MAC CE may be used by introducing a        new LCID. In this case, an MAC CE structure includes a reserved        bit 2105, a serving cell ID 2110, and a BWP ID 2115 and may        include a PUCCH resource group ID 2120 (which is, for example,        four bits but may have an increased number of bits) configured        via RRC and beam information 2125 associated with actual PUCCH        resource transmission. First, a UE may recognize that the MAC CE        is an MAC CE for simultaneous beam updating for a plurality of        PUCCH resources through the LCID. One serving cell and BWP        provided via a previous RRC configuration may be specified        through the MAC CE, and simultaneous beam updating may be        performed for all associated PUCCH resources configured via RRC        through PUCCH resource group information.    -   Referring to FIG. 22 , a new MAC CE may be used by introducing a        new LCID. In this case, an MAC CE structure includes reserved        bits 2230 and 2245, a serving cell ID 2235, and a BWP ID 2240,        and may include a PUCCH resource group ID 2250 (which is, for        example, four bits but may have an increased number of bits)        configured via RRC and beam information 2255 in a bitmap format        associated with actual PUCCH resource transmission. First, a UE        may recognize that the MAC CE is an MAC CE for simultaneous beam        updating for a plurality of PUCCH resources through the LCID.        One serving cell and BWP provided via a previous RRC        configuration may be specified through the MAC CE, and        simultaneous beam updating may be performed for all associated        PUCCH resources configured via RRC through PUCCH resource group        information. Here, regarding the beam information 2255 in the        bitmap format, only one piece may be set to 1, and a plurality        of entities may be set to 1 when PUCCH transmission through a        plurality of beams is required.

FIG. 23 illustrates an MAC CE structure according to an embodiment ofthe disclosure.

FIG. 24 illustrates an MAC CE structure according to an embodiment ofthe disclosure.

FIG. 25 illustrates an MAC CE structure according to an embodiment ofthe disclosure.

FIG. 26 illustrates an MAC CE structure according to an embodiment ofthe disclosure.

In an embodiment of the disclosure, simultaneous beam updating for aPUCCH resource group is supported through an MAC CE without an RRCconfiguration. For example, since PUCCH resource group information isnot provided in advance through an RRC configuration, the MAC CE needsto include all relevant information (i.e., about a plurality of PUCCHresources) for simultaneous beam updating for a plurality of PUCCHresources. The MAC CE has specific structures according to the followingoptions.

-   -   Referring to FIG. 23 , a new MAC CE may be used by introducing a        new LCID. In this case, an MAC CE structure includes a reserved        bit 2305, a serving cell ID 2310, and a BWP ID 2315, and may        include beam information 2320 associated with actual PUCCH        resource transmission. In addition, a list 2325 of PUCCH        resources requiring transmission via a beam actually indicated        in 2320 may be provided. First, a UE may recognize that the MAC        CE is an MAC CE for simultaneous beam updating for a plurality        of PUCCH resources through the LCID. One serving cell and BWP        provided via a previous RRC configuration may be specified        through the MAC CE, and simultaneous beam updating may be        performed for all PUCCH resources indicated through a plurality        of PUCCH resource lists.    -   Referring to FIG. 24 , a new MAC CE may be used by introducing a        new LCID. In this case, an MAC CE structure includes reserved        bits 2430 and 2445, a serving cell ID 2435, and a BWP ID 2440,        and may include beam information 2450 associated with actual        PUCCH resource transmission. In addition, a list 2455 of PUCCH        resources requiring transmission via a beam actually indicated        in 2450 may be provided in a bitmap format. First, a UE may        recognize that the MAC CE is an MAC CE for simultaneous beam        updating for a plurality of PUCCH resources through the LCID.        One serving cell and BWP provided via a previous RRC        configuration may be specified through the MAC CE, and        simultaneous beam updating may be performed for all PUCCH        resources indicated through a plurality of PUCCH resource lists.        Here, regarding beam information (i.e., the list 2455) in the        bitmap format, only one piece may be set to 1, and a plurality        of entities may be set to 1 when PUCCH transmission through a        plurality of beams is required.    -   Referring to FIG. 25 , a new MAC CE may be used by introducing a        new LCID. In this case, an MAC CE structure may include a        reserved bit 2560, a serving cell ID 2565, and a BWP ID 2570,        and may include the total number 2575 of PUCCH resource sets for        which corresponding beam updating is performed and beam        information 2580 associated with actual PUCCH resource        transmission. In addition, a list 2585 of PUCCH resource sets        requiring transmission via a beam actually indicated in beam        information 2580 may be provided. First, a UE may recognize that        the MAC CE is an MAC CE for simultaneous beam updating for a        plurality of PUCCH resources through the LCID. One serving cell        and BWP provided via a previous RRC configuration may be        specified through the MAC CE, and simultaneous beam updating may        be performed for all PUCCH resources indicated through a        plurality of PUCCH resource set lists.    -   Referring to FIG. 26 , a new MAC CE may be used by introducing a        new LCID. In this case, an MAC CE structure may include reserved        bits 2690, 2693, and 2695, a serving cell ID 2691, and a BWP ID        2692, and may include beam information 2694 associated with        actual PUCCH resource transmission. In addition, a list 2696 of        PUCCH resource sets requiring transmission via a beam actually        indicated in beam information 2694 may be provided in a bitmap        format. First, a UE may recognize that the MAC CE is an MAC CE        for simultaneous beam updating for a plurality of PUCCH        resources through the LCID. One serving cell and BWP provided        via a previous RRC configuration may be specified through the        MAC CE, and simultaneous beam updating may be performed for all        PUCCH resources indicated through a plurality of PUCCH resource        set lists. Here, regarding beam information (i.e., the list        2696) in the bitmap format, only one piece may be set to 1, and        a plurality of entities may be set to 1 when PUCCH transmission        through a plurality of beams is required.

FIG. 27 illustrates an overall operation of a base station according toan embodiment of the disclosure.

Referring to FIG. 27 , in operation 2705, the base station may establishan RRC connection state with a UE. In operation 2710, the base stationmay request a UE capability from the UE and may receive corresponding UEcapability information. The base station may analyze the UE capabilityreceived in the above operation and may determine whether the UE has acapability of simultaneous beam updating for a plurality of PUCCHresources. Further, the base station may identify whether the basestation has configured a corresponding function. Then, in operation2715, the base station may provide configuration information aboutsimultaneous beam updating for a plurality of PUCCH resources accordingto the UE capability to the UE through an RRC message. This operationcorresponds to the third embodiment and additional operation is providedin this operation in the fourth embodiment. When the UE does not havethe corresponding capability or the base station determines that acorresponding configuration is not necessary, the base station mayprovide configuration information for beam updating for basic PUCCHresources rather than providing the configuration information needed forsimultaneous beam updating for a plurality of PUCCH resources.

In operation 2720, the base station may indicate beam updating bytransmitting a beam-updating MAC CE for simultaneous beam updating for aplurality of PUCCH resources based on a PUCCH resource configuration andrelated beam configuration information (information necessary forsimultaneous beam updating for a plurality of PUCCH resources)configured via RRC. In this operation, an existing beam indication MACCE for a PUCCH resource may be used. In operation 2725, the base stationmay receive a PUCCH resource and may perform data communicationaccording to a configured and indicated beam.

FIG. 28 is a block diagram illustrating an internal structure of a UEaccording to an embodiment of the disclosure.

Referring to FIG. 28 , the UE includes a radio frequency (RF) processor2810, a baseband processor 2820, a storage unit 2830, and a controller2840.

The RF processor 2810 performs a function for transmitting or receivinga signal through a wireless channel, such as band conversion andamplification of a signal. That is, the RF processor 2810 up converts abaseband signal, provided from the baseband processor 2820, into an RFband signal to transmit the RF band signal through an antenna, and downconverts an RF band signal, received through the antenna, into abaseband signal. For example, the RF processor 2810 may include atransmission filter, a reception filter, an amplifier, a mixer, anoscillator, a digital-to-analog converter (DAC), and ananalog-to-digital converter (ADC). Although FIG. 28 shows only oneantenna, the UE may include a plurality of antennas. In addition, the RFprocessor 2810 may include a plurality of RF chains. Further, the RFprocessor 2810 may perform beamforming. For beamforming, the RFprocessor 2810 may adjust the phase and strength of each of signalstransmitted and received through a plurality of antennas or antennaelements. The RF processor 2810 may perform MIMO and may receive aplurality of layers when performing MIMO.

The baseband processor 2820 performs a function of converting a basebandsignal and a bit stream according to the physical-layer specification ofa system. For example, in data transmission, the baseband processor 2820encodes and modulates a transmission bit stream, thereby generatingcomplex symbols. In data reception, the baseband processor 2820demodulates and decodes a baseband signal, provided from the RFprocessor 2810, thereby reconstructing a reception bit stream. Forexample, according to OFDM, in data transmission, the baseband processor2820 generates complex symbols by encoding and modulating a transmissionbit stream, maps the complex symbols to subcarriers, and constructs OFDMsymbols through an inverse fast Fourier transform (IFFT) and cyclicprefix (CP) insertion. In data reception, the baseband processor 2820divides a baseband signal, provided from the RF processor 2810, intoOFDM symbols, reconstructs signals mapped to subcarriers through a fastFourier transform (FFT), and reconstructs a reception bit stream throughdemodulation and decoding.

As described above, the baseband processor 2820 and the RF processor2810 transmit and receive signals. Accordingly, the baseband processor2820 and the RF processor 2810 may be referred to as a transmitter, areceiver, a transceiver, or a communication unit. At least one of thebaseband processor 2820 and the RF processor 2810 may include aplurality of communication modules to support a plurality of differentradio access technologies. Further, at least one of the basebandprocessor 2820 and the RF processor 2810 may include differentcommunication modules for processing signals in different frequencybands. For example, the different radio access technologies may includea wireless LAN (for example, IEEE 802.11), a cellular network (forexample, an LTE network), and the like. In addition, the differentfrequency bands may include a super high frequency (SHF) band (e.g., 2.NRHz or NRhz) and a millimeter wave band (e.g., 60 GHz).

The storage unit 2830 stores data, such as a default program, anapplication, and configuration information for operating the UE. Inparticular, the storage unit 2830 may store information on a secondaccess node performing wireless communication using a second radioaccess technology. The storage unit 2830 provides stored data uponrequest from the controller 2840.

The controller 2840 controls overall operations of the UE. For example,the controller 2840 transmits and receives signals through the basebandprocessor 2820 and the RF processor 2810. Further, the controller 2840records and reads data in the storage unit 2830. To this end, thecontroller 2840 may include at least one processor. For example, thecontroller 2840 may include a communication processor (CP) (e.g.,multi-connection processor 2842) to perform control for communicationand an application processor (AP) to control an upper layer, such as anapplication. The controller 2840, the baseband processor 2820, the RFprocessor 2810, and the storage unit 2830 may be electrically connected.

FIG. 29 is a block diagram illustrating a configuration of an NR basestation according to an embodiment of the disclosure.

Referring to FIG. 29 , the base station includes an RF processor 2910, abaseband processor 2920, a backhaul communication unit 2930, a storageunit 2940, and a controller 2950.

The RF processor 2910 performs a function for transmitting or receivinga signal through a wireless channel, such as band conversion andamplification of a signal. That is, the RF processor 2910 up converts abaseband signal, provided from the baseband processor 2920, into an RFband signal to transmit the RF band signal through an antenna, and downconverts an RF band signal, received through the antenna, into abaseband signal. For example, the RF processor 2910 may include atransmission filter, a reception filter, an amplifier, a mixer, anoscillator, a DAC, and an ADC. Although FIG. 29 shows only one antenna,the base station may include a plurality of antennas. In addition, theRF processor 2910 may include a plurality of RF chains. Further, the RFprocessor 2910 may perform beamforming. For beamforming, the RFprocessor 2910 may adjust the phase and strength of each of signalstransmitted and received through a plurality of antennas or antennaelements. The RF processor 2910 may transmit one or more layers, therebyperforming downlink MIMO.

The baseband processor 2920 performs a function of converting a basebandsignal and a bit stream according to the physical-layer specification ofa first radio access technology. For example, in data transmission, thebaseband processor 2920 encodes and modulates a transmission bit stream,thereby generating complex symbols. In data reception, the basebandprocessor 2920 demodulates and decodes a baseband signal, provided fromthe RF processor 2910, thereby reconstructing a reception bit stream.For example, according to OFDM, in data transmission, the basebandprocessor 2920 generates complex symbols by encoding and modulating atransmission bit stream, maps the complex symbols to subcarriers, andconstructs OFDM symbols through an IFFT and CP insertion. In datareception, the baseband processor 2920 divides a baseband signal,provided from the RF processor 2910, into OFDM symbols, reconstructssignals mapped to subcarriers through an FFT, and reconstructs areception bit stream through demodulation and decoding. As describedabove, the baseband processor 2920 and the RF processor 2910 transmitand receive signals. Accordingly, the baseband processor 2920 and the RFprocessor 2910 may be referred to as a transmitter, a receiver, atransceiver, a communication unit, or a wireless communication unit.

The backhaul communication unit 2930 provides an interface forperforming communication with other nodes in a network. That is, thebackhaul communication unit 2930 may convert a bit stream, transmittedfrom the base station to another node, for example, a secondary basestation or a core network, into a physical signal, and may convert aphysical signal, received from the other node, into a bit stream.

The storage unit 2940 stores data, such as a default program, anapplication, and configuration information for operating the basestation. In particular, the storage unit 2940 may store information on abearer allocated to a connected UE, a measurement result reported from aconnected UE, and the like. In addition, the storage unit 2940 may storeinformation as a criterion for determining whether to provide or stop amulti-connection to a UE. The storage unit 2940 provides stored dataupon request from the controller 2950.

The controller 2950 controls overall operations of the base station. Forexample, the controller 2950 transmits and receives signals through thebaseband processor 2920 and the RF processor 2910 or through thebackhaul communication unit 2930. Further, the controller 2950 recordsand reads data in the storage unit 2940. To this end, the controller2950 may include at least one processor (e.g., a multi-connectionprocessor 2952). The controller 2950, the RF processor 2910, thebaseband processor 2920, the backhaul communication unit 2930, and thestorage unit 2940 may be electrically connected.

Methods disclosed in the claims and/or methods according to variousembodiments described in the specification of the disclosure may beimplemented by hardware, software, or a combination of hardware andsoftware.

When the methods are implemented by software, a computer-readablestorage medium for storing one or more programs (software modules) maybe provided. The one or more programs stored in the computer-readablestorage medium may be configured for execution by one or more processorswithin the electronic device. The at least one program may includeinstructions that cause the electronic device to perform the methodsaccording to various embodiments of the disclosure as defined by theappended claims and/or disclosed herein.

The programs (software modules or software) may be stored innon-volatile memories including a random access memory and a flashmemory, a read only memory (ROM), an electrically erasable programmableread only memory (EEPROM), a magnetic disc storage device, a compactdisc-ROM (CD-ROM), digital versatile discs (DVDs), or other type opticalstorage devices, or a magnetic cassette. Alternatively, any combinationof some or all of them may form a memory in which the program is stored.Further, a plurality of such memories may be included in the electronicdevice.

In addition, the programs may be stored in an attachable storage devicewhich may access the electronic device through communication networkssuch as the Internet, Intranet, Local Area Network (LAN), Wide LAN(WLAN), and Storage Area Network (SAN) or a combination thereof. Such astorage device may access the electronic device via an external port.Further, a separate storage device on the communication network mayaccess a portable electronic device.

In the above-described detailed embodiments of the disclosure, anelement included in the disclosure is expressed in the singular or theplural according to presented detailed embodiments. However, thesingular form or plural form is selected appropriately to the presentedsituation for the convenience of description, and the disclosure is notlimited by elements expressed in the singular or the plural. Therefore,either an element expressed in the plural may also include a singleelement or an element expressed in the singular may also includemultiple elements.

Although specific embodiments have been illustrated in the detaileddescription of the disclosure, different modifications may be possiblewithout departing from the scope of the disclosure. Therefore, the scopeof the disclosure will be defined not by the described embodiments butby the appended claims to be mentioned and equivalents thereto.

What is claimed is:
 1. A method performed by a terminal in a wirelesscommunication system, the method comprising: receiving, from a basestation, a radio resource control (RRC) message including information onmapping between sounding reference signal resource indicator (SRI)physical uplink shared channel (PUSCH) power control identifier (ID) andPUSCH pathloss reference reference signal (RS) ID values; receiving,from the base station, downlink control information (DCI) including anSRI; identifying a pathloss based on the DCI; and transmitting, to thebase station, a PUSCH based on the identified pathloss, wherein themapping is updated by a medium access control (MAC) control element (CE)received from the base station, and wherein the MAC CE includes: firstinformation indicating a PUSCH pathloss reference RS ID which is to beupdated in the mapping, second information indicating an SRI PUSCH powercontrol ID mapped to the PUSCH pathloss reference RS ID, and thirdinformation indicating a presence of an additional SRI PUSCH powercontrol ID mapped to the PUSCH pathloss reference RS ID.
 2. The methodof claim 1, wherein a number of the PUSCH pathloss reference RS IDvalues is configured up to
 64. 3. The method of claim 1, wherein the MACCE further includes information on a serving cell ID and information ona bandwidth part ID.
 4. The method of claim 1, wherein the MAC CE isidentified by a new logical channel ID value.
 5. The method of claim 1,wherein the identifying of the pathloss based on the DCI comprises:identifying an RS for pathloss mapped to the SRI of the DCI; andidentifying the pathloss using the identified RS for pathloss.
 6. Amethod performed by a base station in a wireless communication system,the method comprising: transmitting, to a terminal, a radio resourcecontrol (RRC) message including information on mapping between soundingreference signal resource indicator (SRI) physical uplink shared channel(PUSCH) power control identifier (ID) and PUSCH pathloss referencereference signal (RS) ID values; transmitting, to the terminal, a mediumaccess control (MAC) control element (CE) for updating the mapping; andtransmitting, to the terminal, downlink control information (DCI)including an SRI, wherein the MAC CE includes: first informationindicating a PUSCH pathloss reference RS ID which is to be updated inthe mapping, second information indicating an SRI PUSCH power control IDmapped to the PUSCH pathloss reference RS ID, and third informationindicating a presence of an additional SRI PUSCH power control ID mappedto the PUSCH pathloss reference RS ID.
 7. The method of claim 6, whereina number of the PUSCH pathloss reference RS ID values is configured upto
 64. 8. The method of claim 6, wherein the MAC CE further includesinformation on a serving cell ID and information on a bandwidth part ID.9. The method of claim 6, wherein the MAC CE is generated based on a newlogical channel ID value.
 10. The method of claim 6, wherein the SRI ofthe DCI is mapped to an RS for pathloss, and a pathloss for the PUSCH isassociated with the RS for pathloss.
 11. A terminal in a wirelesscommunication system, the terminal comprising: a transceiver; and acontroller configured to: receive, from a base station via thetransceiver, a radio resource control (RRC) message includinginformation on mapping between sounding reference signal resourceindicator (SRI) physical uplink shared channel (PUSCH) power controlidentifier (ID) and PUSCH pathloss reference reference signal (RS) IDvalues, receive, from the base station via the transceiver, downlinkcontrol information (DCI) including an SRI, identify a pathloss based onthe DCI, and transmit, to the base station via the transceiver, a PUSCHbased on the identified pathloss, wherein the mapping is updated by amedium access control (MAC) control element (CE) received from the basestation, and wherein the MAC CE includes: first information indicating aPUSCH pathloss reference RS ID which is to be updated in the mapping,second information indicating an SRI PUSCH power control ID mapped tothe PUSCH pathloss reference RS ID, and third information indicating apresence of an additional SRI PUSCH power control ID mapped to the PUSCHpathloss reference RS ID.
 12. The terminal of claim 11, wherein a numberof the PUSCH pathloss reference RS ID values is configured up to
 64. 13.The terminal of claim 11, wherein the MAC CE further includesinformation on a serving cell ID and information on a bandwidth part ID.14. The terminal of claim 11, wherein the MAC CE is identified by a newlogical channel ID value.
 15. The terminal of claim 11, wherein thecontroller is further configured to: identify an RS for pathloss mappedto the SRI of the DCI, and identify the pathloss using the identified RSfor pathloss.
 16. A base station in a wireless communication system, thebase station comprising: a transceiver; and a controller configured to:transmit, to a terminal via the transceiver, a radio resource control(RRC) message including information on mapping between soundingreference signal resource indicator (SRI) physical uplink shared channel(PUSCH) power control identifier (ID) and PUSCH pathloss referencereference signal (RS) ID values, transmit, to the terminal via thetransceiver, a medium access control (MAC) control element (CE) forupdating the mapping, and transmit, to the terminal via the transceiver,downlink control information (DCI) including an SRI, wherein the mappingis updated by a medium access control (MAC) control element (CE)received from the base station, and wherein the MAC CE includes: firstinformation indicating a PUSCH pathloss reference RS ID which is to beupdated in the mapping, second information indicating an SRI PUSCH powercontrol ID mapped to the PUSCH pathloss reference RS ID, and thirdinformation indicating a presence of an additional SRI PUSCH powercontrol ID mapped to the PUSCH pathloss reference RS ID.
 17. The basestation of claim 16, wherein a number of the PUSCH pathloss reference RSID values is configured up to
 64. 18. The base station of claim 16,wherein the MAC CE further includes information on a serving cell ID andinformation on a bandwidth part ID.
 19. The base station of claim 16,wherein the MAC CE is generated based on a new logical channel ID value.20. The base station of claim 16, wherein the SRI of the DCI is mappedto an RS for pathloss, and a pathloss for the PUSCH is associated withthe RS for pathloss.